Add a cluster using cluster certificates (deprecated)
Deprecated in GitLab 14.0.
Disable a cluster
When you successfully connect an existing cluster using cluster certificates, the cluster connection to GitLab becomes enabled. To disable it:
- Go to your:
- Project’s Infrastructure > Kubernetes clusters page, for a project-level cluster.
- Group’s Kubernetes page, for a group-level cluster.
- Main menu > Admin > Kubernetes page, for an instance-level cluster.
- Select the name of the cluster you want to disable.
- Toggle GitLab Integration off (in gray).
- Select Save changes.
Remove a cluster
Introduced in GitLab 12.6, you can remove cluster integrations and resources.
When you remove a cluster integration, you only remove the cluster relationship
to GitLab, not the cluster. To remove the cluster itself, go to your cluster’s
GKE or EKS dashboard to do it from their UI or use
You need at least Maintainer permissions to your project or group to remove the integration with GitLab.
When removing a cluster integration, you have two options:
- Remove integration: remove only the Kubernetes integration.
- Remove integration and resources: remove the cluster integration and all GitLab cluster-related resources such as namespaces, roles, and bindings.
To remove the Kubernetes cluster integration:
- Go to your cluster details page.
- Select the Advanced Settings tab.
- Select either Remove integration or Remove integration and resources.
Remove clusters by using the Rails console
Start a Rails console session.
To find a cluster:
cluster = Clusters::Cluster.find(1) cluster = Clusters::Cluster.find_by(name: 'cluster_name')
To delete a cluster but not the associated resources:
# Find users who have administrator access user = User.find_by(username: 'admin_user') # Find the cluster with the ID cluster = Clusters::Cluster.find(1) # Delete the cluster Clusters::DestroyService.new(user).execute(cluster)