## Release notes The GitLab Kubernetes Agent provides a secure connection to any Kubernetes cluster and is the recommended approach to integrate a cluster with GitLab for deployments and monitoring. Since GitLab 14.1, GitLab users can use the agent for pull and push based deployments as well. The push based deployments allow GitLab CI users to deploy to a cluster using their well-known GitLab pipelines. Until now, this feature enabled pushing to a cluster only from the same project where the Kubernetes Agent was registered. The current release enables agent's to be marked as a group level agent. As a result, every project under the given group receives access to the cluster connection for deployments or other commands. ## Scope Allow agents to grant access to groups. Any project within that group can access Kubernetes via the given Agent. Do we expect the Agent to be in that group? No. Do we allow an agent to allow access to more than one group? Yes. Once the agent configuration enables access to a group, all the projects within that group can access the agent. The correct `kubeconfig` still has to be set up / selected in CI. Thus, having a group side settings is not in scope in the current iteration. * [x] Implement a group id -> agent id index * [x] Implement most specific group/project selection logic