Connect a cluster to GitLab
Tier: Free, Premium, Ultimate
Offering: GitLab.com, Self-managed, GitLab Dedicated
The certificate-based Kubernetes integration with GitLab was deprecated in GitLab 14.5. To connect your clusters, use the GitLab agent.
Cluster levels (deprecated)
History
- Deprecated in GitLab 14.5.
The concept of cluster levels was deprecated
in GitLab 14.5.
Choose your cluster’s level according to its purpose:
| Level | Purpose |
|---|---|
| Project level | Use your cluster for a single project. |
| Group level | Use the same cluster across multiple projects within your group. |
| Instance level | Use the same cluster across groups and projects within your instance. |
View your clusters
To view the Kubernetes clusters connected to your project, group, or instance, open the cluster’s page according to your cluster’s level.
Project-level clusters:
- On the left sidebar, select Search or go to and find your project.
- Select Operate > Kubernetes clusters.
Group-level clusters:
- On the left sidebar, select Search or go to and find your group.
- Select Operate > Kubernetes clusters.
Instance-level clusters:
- On the left sidebar, at the bottom, select Admin.
- Select Kubernetes.
Security implications for clusters connected with certificates
History
- Connecting clusters to GitLab through cluster certificates was deprecated in GitLab 14.5.
The whole cluster security is based on a model where developers
are trusted, so only trusted users should be allowed to control your clusters.
The use of cluster certificates to connect your cluster grants access to a wide set of functionalities needed to successfully build and deploy a containerized application. Bear in mind that the same credentials are used for all the applications running on the cluster.