Connect a cluster to GitLab

{{< details >}}

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

{{< /details >}}

The certificate-based Kubernetes integration with GitLab was deprecated in GitLab 14.5. To connect your clusters, use the GitLab agent for Kubernetes.

Cluster levels (deprecated)

{{< history >}}

• Deprecated in GitLab 14.5.

{{< /history >}}

[!warning] 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:

1. In the top bar, select Search or go to and find your project.
2. Select Operate > Kubernetes clusters.

Group-level clusters:

1. In the top bar, select Search or go to and find your group.
2. Select Operate > Kubernetes clusters.

Instance-level clusters:

Prerequisites:

• Administrator access.

1. In the upper-right corner, select Admin.
2. Select Kubernetes.

Security implications for clusters connected with certificates

{{< history >}}

• Connecting clusters to GitLab through cluster certificates was deprecated in GitLab 14.5.

{{< /history >}}

[!warning] 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.