Use agent name as the helm release name in the generated command
Release notes
Problem to solve
There is a snippet produced to install the Kubernetes Agent. It is something along the lines of:
helm upgrade --install gitlab-agent gitlab/gitlab-agent --namespace gitlab-agent --create-namespace --set config.token=<token> --set config.kasAddress=wss://kas.gitlab.com
The problem is that when a user installs multiple agents in the same cluster, the helm upgrade --install
command will overwrite the old installation with just a different token, effectively breaking the old agent (as there is no installation for that token anymore).
Proposal
To minimize the risk of conflict, use the agent name as the helm release name. For example, in the above command, change gitlab-agent
to <agent-name>
:
helm upgrade --install <agent-name> gitlab/gitlab-agent --namespace gitlab-agent --create-namespace --set config.token=<token> --set config.kasAddress=wss://kas.gitlab.com
This also makes the snippet more developer friendly as each agent is easier to identify in the cluster afterwards.
Intended users
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.