Enable registering multiple Agents against the same agent configuration

Release notes

Managing multi-region clusters requires an easy way to change all the clusters at once. Until now, the GitLab Kubernetes integration required cluster administrators to create a separate agent configuration for every Agent. The current change enables the re-use of agent configurations by multiple agents, and enables easy multi-region setups where the resources on the clusters should be identical.

Problem to solve

As a Platform engineer, I want to use the same configuration for multiple agentk instances to support multi-region setups within my environments.

Today, the agent name equals the directory name under .gitlab/agents. This makes the agent names unique by design. At the same time, this prohibits to use the same agent configuration, for example .gitlab/agents/production by multiple agents, like prod-eu and prod-us.

Proposal

Alternative 1

At the Agent registration view / API, allow users to select any of the existing agent configurations. At the same time, request a unique agent name that will identify the Agent.

Alternative 2

Implement an include key in the Agent configuration syntax to re-use Agent configuration "partials" stored within the repository.

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.