Kubernetes clusters (FREE)
To connect clusters to GitLab, use the GitLab Agent.
Certificate-based Kubernetes integration (DEPRECATED)
The certificate-based Kubernetes integration with GitLab is deprecated. It had the following issues:
- There were security issues as it required direct access to the Kube API by GitLab.
- The configuration options weren't flexible.
- The integration was flaky.
- Users were constantly reporting issues with features based on this model.
For this reason, we started to build features based on a new model, the GitLab Agent. Maintaining both methods in parallel caused a lot of confusion and significantly increased the complexity to use, develop, maintain, and document them. For this reason, we decided to deprecate them to focus on the new model.
Certificate-based features will continue to receive security and critical fixes, and features built on top of it will continue to work with the supported Kubernetes versions. The removal of these features from GitLab is not scheduled yet. Follow this epic for updates.
You can find technical information about why we moved away from cluster certificates into the GitLab Agent model on the Agent's blueprint documentation.
- Create a new cluster through cluster certificates
- Connect an existing cluster through cluster certificates
- Access controls
- GitLab-managed clusters
- GitLab Managed Apps
- Deploy applications through certificate-based connection
- Cluster Management Project
- Cluster integrations
- Cluster cost management
- Cluster environments
- Advanced traffic control with Canary Ingress
- Deploy Boards
- Pod logs
- Clusters health
- Crossplane integration
- Web terminals
The Agent is always configured in a single GitLab project, but you can use the CI/CD Tunnel to authorize other projects and groups to use the same Agent. By doing so, you are granting these projects and groups access to the same cluster, which is similar to group-level clusters' use case.