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
2ba2f1e5
Commit
2ba2f1e5
authored
Jan 03, 2022
by
alexandra
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
CI/CD Tunnel: clarify context naming scheme
parent
3267b1fc
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/user/clusters/agent/ci_cd_tunnel.md
doc/user/clusters/agent/ci_cd_tunnel.md
+1
-1
No files found.
doc/user/clusters/agent/ci_cd_tunnel.md
View file @
2ba2f1e5
...
...
@@ -32,7 +32,7 @@ jobs provide a `KUBECONFIG` variable compatible with `kubectl`.
Also, each Agent has a separate context (
`kubecontext`
). By default,
there isn't any context selected.
Contexts are named in the following format:
`<
agent-configuration-project-path
>:<agent-name>`
.
Contexts are named in the following format:
`<
namespace>/<project-name
>:<agent-name>`
.
To get the list of available contexts, run
`kubectl config get-contexts`
.
## Share the CI/CD Tunnel provided by an Agent with other projects and groups
...
...
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