Cloud provider setup for the GitLab chart

Tier: Free, Premium, Ultimate Offering: 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 End of life
1.30 In development/qualification 17.0 x86-64 2025-06-28
1.29 Supported 17.0 x86-64 2025-02-28
1.28 Supported 17.0 x86-64 2024-10-28
1.27 Supported 16.6 x86-64 2024-06-28
1.26 Deprecated 16.5 x86-64 2024-02-28
1.25 Deprecated 16.5 x86-64 2023-10-28
1.24 Deprecated 16.5 x86-64 2023-07-28
1.23 Deprecated 16.5 x86-64 2023-02-28
1.22 Deprecated 16.5 x86-64 2022-10-28

The GitLab Helm Chart aims to support new minor Kubernetes releases three months after their initial release. 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 must use the x86-64 architecture. Support for multiple architectures, including AArch64/ARM64, is under active development. See issue 2899 for more information.

Instructions for specific Cloud providers

Create and connect to a Kubernetes cluster in your environment: