Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
9c72f8fd
Commit
9c72f8fd
authored
Sep 27, 2017
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Resolve kubernetes docs conflicts
parent
0a4de96e
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
31 deletions
+0
-31
doc/user/project/integrations/kubernetes.md
doc/user/project/integrations/kubernetes.md
+0
-31
No files found.
doc/user/project/integrations/kubernetes.md
View file @
9c72f8fd
...
...
@@ -19,36 +19,6 @@ for the changes to take effect.
![
Kubernetes configuration settings
](
img/kubernetes_configuration.png
)
<<<<<<< HEAD
The Kubernetes service takes the following arguments:
1.
API URL
1.
Custom CA bundle
1.
Kubernetes namespace
1.
Service token
The API URL is the URL that GitLab uses to access the Kubernetes API. Kubernetes
exposes several APIs - we want the "base" URL that is common to all of them,
e.g.,
`https://kubernetes.example.com`
rather than
`https://kubernetes.example.com/api/v1`
.
A [namespace] is just a logical grouping of resources. This is mostly for ease of
management, so you can group things together. For example, if you have 50
projects using the same cluster, providing a simple list of all pods would be
really difficult to work with. In that case, you can provide a separate
namespace to group things, as well as reduce name collision issues.
GitLab authenticates against Kubernetes using service tokens, which are
scoped to a particular
`namespace`
. If you don't have a service token yet,
you can follow the
[
Kubernetes documentation
](
http://kubernetes.io/docs/user-guide/service-accounts/
)
to create one. You can also view or create service tokens in the
[
Kubernetes dashboard
](
http://kubernetes.io/docs/user-guide/ui/
)
- visit
**Config ➔ Secrets**
.
Fill in the service token and namespace according to the values you just got.
If the API is using a self-signed TLS certificate, you'll also need to include
the `ca.crt` contents as the `Custom CA bundle`.
=======
The Kubernetes service takes the following parameters:
-
**API URL**
-
...
...
@@ -76,7 +46,6 @@ The Kubernetes service takes the following parameters:
to create one. You can also view or create service tokens in the
[
Kubernetes dashboard
](
https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/#config
)
(under
**Config > Secrets**
).
>>>>>>> upstream/master
[
namespace
]:
https://kubernetes.io/docs/user-guide/namespaces/
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment