Connect a cluster to GitLab

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

Supported cluster versions

GitLab is committed to support at least two production-ready Kubernetes minor versions at any given time. We regularly review the versions we support, and provide a three-month deprecation period before we remove support of a specific version. The range of supported versions is based on the evaluation of:

GitLab supports the following Kubernetes versions, and you can upgrade your Kubernetes version to any supported version at any time:

  • 1.20 (support ends on July 22, 2022)
  • 1.19 (support ends on February 22, 2022)
  • 1.18 (support ends on November 22, 2021)
  • 1.17 (support ends on September 22, 2021)

Adding support to other versions of Kubernetes is managed under this epic.

Some GitLab features may support versions outside the range provided here.

Cluster levels (DEPRECATED)

Deprecated in GitLab 14.5.

caution

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. On the top bar, select Menu > Projects and find your project.
  2. On the left sidebar, select Infrastructure > Kubernetes clusters.

Group-level clusters:

  1. On the top bar, select Menu > Groups and find your group.
  2. On the left sidebar, select Kubernetes.

Instance-level clusters:

  1. On the top bar, select Menu > Admin.
  2. On the left sidebar, select Kubernetes.

Security implications for clusters connected with certificates

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

caution
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.