| stage | group | info |
|---|---|---|
Deploy |
Environments |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments |
- Introduced in GitLab 12.3 for group-level clusters.
- Introduced in GitLab 12.4 for instance-level clusters.
- Deprecated in GitLab 14.5.
- Disabled on self-managed in GitLab 15.0.
WARNING: This feature was deprecated in GitLab 14.5.
FLAG:
On self-managed GitLab, by default this feature is not available. To make it available, an administrator can enable the feature flag named certificate_based_clusters.
Cluster environments provide a consolidated view of which CI environments are deployed to the Kubernetes cluster and it:
- Shows the project and the relevant environment related to the deployment.
- Displays the status of the pods for that environment.
With cluster environments, you can gain insight into:
- Which projects are deployed to the cluster.
- How many pods are in use for each project's environment.
- The CI job that was used to deploy to that environment.
Access to cluster environments is restricted to group maintainers and owners
To:
- Track environments for the cluster, you must deploy to a Kubernetes cluster successfully.
- Show pod usage correctly, you must enable deploy boards.
After you have successful deployments to your group-level or instance-level cluster:
- Go to your group's Kubernetes page.
- Select the Environments tab.
Only successful deployments to the cluster are included in this page. Non-cluster environments aren't included.