Cloud provider setup for the GitLab chart

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.

A Kubernetes cluster, running version 1.20 through 1.25, is required because of certain Kubernetes features. 1.25 is supported as of Chart 6.6 (GitLab 15.6). Epic 10785 tracks progress towards supporting 1.26. For some components, like the agent for Kubernetes and GitLab Operator, GitLab might support different cluster versions.

Disabling the in-chart NGINX Ingress Controller (nginx-ingress.enabled=false), allows the use of Kubernetes 1.16 or later. Alternatively, using version 1.2.1 (nginx-ingress.controller.image.tag=v1.2.1) allows the use of Kubernetes 1.19 or later.

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.

Create and connect to a Kubernetes cluster in your environment:

Help & feedback

Docs

Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.

Product

Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Join First Look to help shape new features.

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.

Get Help

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support