This chart contains all the required components to get started and can scale to large deployments. For OpenShift-based installations, use GitLab Operator, otherwise you must update the security context constraints yourself. The GitLab Helm chart requires external PostgreSQL, Redis, and object storage.

Once built, a chart can be uploaded to the desired channel with curl or helm cm-push: ... curl --fail-with-body --request POST \ --form 'chart=@mychart-0.1.0.tgz' \ --user <username>:<access_token> \ https://gitlab.example.com/api/v4/projects/<project_id>/packages/helm/api/<channel>/charts

Example project for testing the new Helm chart repository

August 7, 2026 - Cloud Native GitLab Helm Chart · Read more · GitLab helm k8s + 2 more Kubernetes hacktoberfest · README · MIT License · CHANGELOG · CONTRIBUTING · Created on August 01, 2017 ·

This folder includes files that serve as examples for different configurations for various use cases and customizations of these charts. Copy the needed values.yaml example to the root of this repository ... Let us say we would like to have a basic GitLab installation using the included values-base.yaml. we would be doing the following: ... Change smtp block with our values making sure we have the needed secret. Alternatively we can omit the block completely if we do not need to configure smtp. Finally we save the file · run helm upgrade --install -f values-base.yaml gitlab .

Example project for testing the new Helm chart repository

<CONFIG_VALUES_FILE>: The path to the values file containing your custom configuration. To create it, see Configure GitLab Runner with the Helm chart. <RELEASE-NAME>: The name you gave the chart when you installed it. In the installation section, the example named it gitlab-runner.

For more information, see GitLab Helm Chart provenance. This will output the list of resources installed once the deployment finishes which may take 5-10 minutes. The status of the deployment can be checked by running helm status gitlab which can also be done while the deployment is taking place if you run the command in another terminal. You can access the GitLab instance by visiting the domain specified during installation. The default domain would be gitlab.example...

December 23, 2025 - Helm charts are often the basis for defining the Kubernetes infrastructure. It is clear that for teams dealing with a large number of projects, it makes sense to standardize the way these charts are handled. Starting with GitLab 14.1, it is now possible to configure the storage of shared charts for all the projects you work with. Before GitLab introduced such a feature, you could use, for example, ChartMuseum or store the manifests right inside the repository with the application code instead of a dedicated chart repo.

Example project for testing the new Helm chart repository

Example project for testing the new Helm chart repository

June 22, 2023 - For managing our helm charts we need a token with api, read_registry, and write_registry. Consider saving your token with a safe method in a safer place! ... curl --request POST \ --form 'chart=@my-chart-0.1.0.tgz' \ --user <username>:<access_token> \ https://gitlab.example.com/api/v4/projects/<project_id>/packages/helm/api/<channel>/charts

# adds helm chart repository helm repo add gitlab https://charts.gitlab.io/ helm repo update # searches for the latest version helm search repo -l gitlab # manual: update version number in Chart.yaml # updates Chart.lock helm dependency update

This chart includes all the components for a complete experience, but each part can be installed separately. ... GitLab Pages can be deployed using the Helm chart, but is missing access control.

May 17, 2022 - As we created the project on GitLab, let’s create a simple Helm chart on the local computer by executing the following command: ... Make sure you have installed Helm on your computer. Otherwise, that command won’t execute. The helm create creates a chart directory along with the common files and directories used in a chart. ... The output of the ls command shows that necessary files have been created and we just need to push them to the helm-chart-example project on GitLab.

December 8, 2023 - # clone this repo git clone git@github.com:reactioncommerce/chart-gitlab.git cd chart-gitlab # Copy the default `values.yaml` and fill in your custom options. cp values.yaml custom.values.yaml # Install Gitlab, Docker Registry, and Gitlab Runner helm install --name gitlab --namespace gitlab -f custom.values.yaml ./ # Copy the default nginx-ingress values and set the ssh service name to "gitlab-gitlab" cp nginx-ingress.values.yaml nginx-ingress.custom.values.yaml # Install the Nginx ingress controller # On AWS, this will provision an ELB for you.

December 8, 2023 - Helm charts are often the basis for defining the Kubernetes infrastructure. It is clear that for teams dealing with a large number of projects, it makes sense to standardize the way these charts are handled. Starting with GitLab 14.1, it is now possible to configure the storage of shared charts for all the projects you work with. Before GitLab introduced such a feature, you could use, for example, ChartMuseum or store the manifests right inside the repository with the application code instead of a dedicated chart repo.

Official Helm Chart for the GitLab Runner (https://gitlab.com/gitlab-org/gitlab-runner)

Install GitLab on Kubernetes by using the cloud native GitLab Helm chart.

January 17, 2026 - # charts/my-app/values-production.yaml replicaCount: 3 image: tag: "1.0.0" resources: limits: cpu: 2000m memory: 1Gi ingress: enabled: true hosts: - host: example.com paths: - path: / pathType: Prefix tls: - secretName: production-tls hosts: - example.com · Configure the kubeconfig variables in GitLab CI/CD settings. GitLab provides the registry variables automatically when the container registry is enabled: ... publish-to-gitlab: stage: publish extends: .helm-base script: - | # Use CI_REGISTRY_* variables (automatic) helm registry login -u ${CI_REGISTRY_USER} -p ${CI_REGISTRY_PASSWORD} ${CI_REGISTRY} for chart in ${CHART_DIR}/*/; do helm package "$chart" helm push *.tgz oci://${CI_REGISTRY}/${CI_PROJECT_PATH}/charts rm *.tgz done