<!-- This issue template can be used as a great starting point for feature requests. The section "Release notes" can be used as a summary of the feat ure and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ## Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ## Problem to solve As an Infrastructure Engineer, I want to authorize agent connections at the instance level so that other teams can build their integrations on top of them. As an Infrastructure Engineer, I want to authorize agent connections at the top-level group / organization level on GitLab SaaS, so that other teams can build their integrations on top of them. ## Proposal With the certificate-based Kubernetes cluster integrations deprecated, users must share Kubernetes agents for CI/CD at the project or group level. A 17 seater Ultimate customer has reported([ZD](https://gitlab.zendesk.com/agent/tickets/279173) for internal use) that it's inconvenient for them to set up agents for separate groups in their Org. So, they've requested to bring support for instance-level agents. An internal discussion with @nagyv-gitlab revealed that we do not have instance-level agents in the roadmap, but we're considering adding support for organization-level agents once [organization](https://docs.gitlab.com/ee/architecture/blueprints/organization/) is rolled out. This issue is to track progress on that. ## Intended users * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer) * [Ingrid (Infrastructure Operator)](https://about.gitlab.com/handbook/product/personas/#ingrid-infrastructure-operator) ## Feature Usage Metrics <!-- How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Create tracking issue using the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *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.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->