## Goal 1. Validate with real users that the Kubernetes agent solves real needs (aka product-market fit) 1. Validate that the Kubernetes agents works in a live environment ## Approach We can either: 1. Deploy to GitLab.com, set ultra low limit like 50 or 100; **or** 1. Establish monitoring and dashboards, test on pre-production. Only then, we deploy to GitLab.com ## Release Post candidate With the introduction of the GitLab Kubernetes Agent you get better control and flexibility on integrated Kubernetes clusters. The GitLab Kubernetes Agent is our next iteration of providing outstanding Kubernetes support and integration from within GitLab. The existing solution has two often cited shortcomings that we're addressing with the GitLab Kubernetes Agent: the requirement of `cluster-admin` privileges and opening up your clusters to GitLab. Using the agent, you can get deployments from GitLab to your cluster without giving admin permissions to GitLab. Moreover, the agent watches your cluster state, and synchronizes it when needed with your configured Kubernetes manifests projects. The current version allows access to the agent for GitLab Community members as we're bundling the agent inside the GitLab Development Kit. We want to provide installation via [Omnibus](https://gitlab.com/gitlab-org/gitlab/-/issues/223060) and [Helm charts](https://gitlab.com/gitlab-org/gitlab/-/issues/223061) in the coming months.