Cloud provider setup for the GitLab chart
- Tier: Free, Premium, Ultimate
- Offering: GitLab Self-Managed
Before you deploy the GitLab chart, you must configure resources for the cloud provider you choose.
The GitLab chart is intended to fit in a cluster with at least 8 vCPU and 30 GB of RAM. If you are trying to deploy a non-production instance, you can reduce the defaults to fit into a smaller cluster.
Supported Kubernetes releases
The GitLab Helm chart supports the following Kubernetes releases:
| Kubernetes release | Status | Minimum GitLab version | Architectures |
|---|---|---|---|
| 1.34 | Supported | 18.6 | x86-64 |
| 1.33 | Supported | 18.1 | x86-64 |
| 1.32 | Supported | 17.11 | x86-64 |
| 1.31 | Deprecated | 17.6 | x86-64 |
| 1.30 | Unsupported | 17.6 | x86-64 |
The GitLab Helm Chart aims to support three Kubernetes minor versions at a time and plans to support new Kubernetes releases three months after their initial release.
For more details refer to our Kubernetes support policy.
We welcome reports made to our issue tracker about compatibility issues in releases newer than those listed above.
Some GitLab features might not work on deprecated releases or releases older than the releases listed above.
For some components, like the agent for Kubernetes and GitLab Operator, GitLab might support different cluster releases.
Kubernetes nodes support x86-64 and ARM64 architectures.
FIPS-validated images are only available for x86-64. See issue 2285 for ARM64 FIPS status.
- For cluster topology recommendations for an environment, see the reference architectures.
- For an example of tuning the resources to fit in a 3 vCPU 12 GB cluster, see the minimal GKE example values file.
Instructions for specific Cloud providers
Create and connect to a Kubernetes cluster in your environment: