Add the ability to install the GitLab Kubernetes Agent with Omnibus
Release notes
The GitLab Kubernetes Agent was available only for Helm based installations until now. With the current release, the GitLab Kubernetes Agent can be installed using the Official Linux package too. The previous GitLab Kubernetes integration required your cluster to be open to the Internet for GitLab to access it. For many organizations, this was not possible, because the cluster had to be locked down for security, compliance, or regulatory purposes. To work around these restrictions, users needed to create custom tooling on top of GitLab, or they couldn’t use GitLab features.
Using the GitLab Kubernetes Agent, users can deploy their applications using a pull-based approach, without opening up their clusters to the Internet. The Agent orchestrates deployments by pulling new changes from GitLab, rather than GitLab pushing updates to the cluster. No matter what method of GitOps you use, GitLab has you covered.
The GitLab Kubernetes Agent has a configuration-driven setup, and enables deployment management by code. Some existing Kubernetes integration features, such as Deploy Boards and GitLab Managed Apps, are not yet supported. Our vision is to eventually implement these capabilities, and provide new security- and compliance-focused integrations with the Agent.
Problem to solve
Add the ability to install the GitLab Kubernetes Agent with Omnibus
Assumption
Assuming GitLab.com is installed using Omnibus.
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.