<!-- 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 feature 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 a self-managed GitLab user, I need to deploy to my in-cloud clusters that can not access GitLab directly. On the other hand, GitLab can access these clusters. ## Proposal For self-managed GitLab users allow to enable a feature flag/config option that would make it possible to provide agent's URL when registering an agent. kas can connect to such agents: - to establish reverse tunnels so that agents can talk to kas (e.g. to pull configuration, etc). - to make requests for CI tunnel functionality. Technical design is in https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/blob/master/doc/kas_to_agentk_connectivity.md. ## Intended users - Infrastructure Engineeer - Self-managed only ## Tiering ~"GitLab Ultimate" only as this serves users with high security requirements who are restricted from creating a VPN with their cloud provider. We expect such company-wide regulations to come from executive levels. See the [GitLab buyer-based pricing model](https://about.gitlab.com/company/pricing/#buyer-based-tiering-clarification) for more details. ## 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 --> ### References - https://gitlab.com/groups/gitlab-org/configure/-/epics/8+ <!-- 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 -->