🌐
GitLab
docs.gitlab.com › gitlab docs › install › installation methods › helm chart
GitLab Helm chart | GitLab Docs
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 ...
GitLab Docs
If you're using cluster management, we recommend the Helm chart or the Operator for installing cloud-native GitLab.
Upgrade GitLab
Upgrade GitLab to later versions
Install GitLab Runner
Install GitLab Runner in Kubernetes using the GitLab Helm chart.
Configure GitLab Runner
Advanced configuration options: Use the config.toml configuration file to edit runner settings · Use self-signed certificates: Configure certificates that verify TLS peers when connecting to the GitLab server · Autoscale with Docker Machine: Execute jobs on machines created automatically ...
🌐
GitLab
gitlab.com › gitlab.org › charts › gitlab chart
GitLab.org / charts / GitLab Chart · GitLab
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 ·
🌐
GitLab
docs.gitlab.com › gitlab docs › use gitlab › deploy and release your application › packages & registries › package registry › helm
Helm charts in the package registry | GitLab Docs
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
🌐
GitLab
docs.gitlab.com › gitlab docs › install › install gitlab runner › helm chart
GitLab Runner Helm chart | GitLab Docs
The GitLab Runner Helm chart is the official way to deploy a GitLab Runner instance into your Kubernetes cluster.
🌐
GitLab
gitlab.com › gitlab.org › charts
charts · GitLab
Helm chart for the client-side component (agentk) of the GitLab Agent for Kubernetes.
Find elsewhere
🌐
OneUptime
oneuptime.com › home › blog › helm chart ci/cd with gitlab ci
Helm Chart CI/CD with GitLab CI
January 17, 2026 - GitLab CI provides a complete platform for Helm chart CI/CD with built-in container registry, Kubernetes integration, and environment management. Use stages for lint, test, build, security, publish, and deploy. Leverage GitLab's container registry for chart storage, configure environment-specific values files, and use manual gates for production deployments.
🌐
GitLab
docs.gitlab.com › charts › installation › command-line-options
GitLab Helm chart deployment options | GitLab Docs
This page lists commonly used values of the GitLab chart. For a complete list of the available options, refer to the documentation for each subchart. You can pass values to the helm install command by using a YAML file and the --values <values file> flag or by using multiple --set flags.
🌐
GitLab
gitlab.com › gitlab.org › charts › gitlab runner
GitLab.org / charts / GitLab Runner · GitLab
Official Helm Chart for the GitLab Runner (https://gitlab.com/gitlab-org/gitlab-runner)
🌐
Palark
palark.com › home › blog › ci/cd › using gitlab as a convenient helm charts repository
Using GitLab as a convenient Helm charts repository | Tech blog | Palark
December 23, 2025 - 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. Sure, it didn’t have any obvious shortcomings in terms of functionality. Still, standardizing the project layout didn’t turn out to be such a picnic as the repository turned into a big mess over time. On the other hand, the GitLab Helm repo allows you to store commonly used Helm charts for popular infrastructure components as well as the files needed to run your app in Kubernetes in a shared repository in your corporate GitLab account.
🌐
GitHub
github.com › nuttingd › gitlab-helm-chart › blob › master › doc › index.md
gitlab-helm-chart/doc/index.md at master · nuttingd/gitlab-helm-chart
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.
Author: nuttingd
🌐
Iws
fwd.iws.edu › en › gitlab-helm-chart.html
Gitlab Helm Chart - Printable Study Planner
November 2, 2025 - Find out how to configure, deploy, and troubleshoot the chart components and subcharts. This chart contains all the required components to get started and can scale to large. Web cloud native gitlab helm chart. See the default and recommended values for basic configuration, tls, outgoing.
🌐
GitHub
github.com › lwolf › gitlab-chart
GitHub - lwolf/gitlab-chart: Kubernetes Helm chart to deploy GitLab · GitHub
Kubernetes Helm chart to deploy GitLab. Contribute to lwolf/gitlab-chart development by creating an account on GitHub.
Author: lwolf
🌐
Reddit
reddit.com › r/gitlab › i'm confused about the gitlab helm chart warning
r/gitlab on Reddit: I'm confused about the Gitlab Helm chart warning
November 6, 2024 -

The Gitlab Helm chart deploy page says "The default Helm chart configuration is not intended for production. The default chart creates a proof of concept (PoC) implementation where all GitLab services are deployed in the cluster. For production deployments, you must follow the Cloud Native Hybrid reference architecture." in a warning box.

What do they mean exactly with production? Like don't use it in a production K8s cluster so you don't interfere with your production workload or like don't use the Gitlab from the chart as your only, and therefore productive, Gitlab installation because of reasons?

I'm setting up a Kubernetes Cluster in our small company and would like to use Gitlab running in this cluster without having to install it on some dedicated system but I'm confused if I can/should use this Helm chart or not due to this warning.

I hope someone can shed some light on this for me, thanks.

Edit: The Reference architectures | GitLab are completely insane in comparison to us, we're 3 people in the IT. Did I wrongly take the possibility of having Gitlab running in Kubernetes as an actual alternative to the usual installation but it's not at all suitable for us and/or worth the hassle of setting it up? Gitlab also writes "This is an advanced setup. Running services in Kubernetes is well known to be complex. This setup is only recommended if you have strong working knowledge and experience in Kubernetes. The rest of this section assumes this."

🌐
GitLab
about.gitlab.com › blog › devsecops › get started with gitlab's helm package registry
Get started with GitLab's Helm Package Registry
October 18, 2021 - First, add the Helm chart registry to your local CLI configuration and test the manual installation. ... $ helm repo add --username <username> --password <personal_access_token> <REGISTRY_NAME> https://gitlab.com/api/v4/projects/<project_id>/packages/helm/stable $ helm install --name nginx <REGISTRY_NAME>/nginx
🌐
Palark
blog.palark.com › home › using gitlab as a convenient helm charts repository
Using GitLab as a convenient Helm charts repository – Palark | Blog
December 8, 2023 - 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. Sure, it didn’t have any obvious shortcomings in terms of functionality. Still, standardizing the project layout didn’t turn out to be such a picnic as the repository turned into a big mess over time. On the other hand, the GitLab Helm repo allows you to store commonly used Helm charts for popular infrastructure components as well as the files needed to run your app in Kubernetes in a shared repository in your corporate GitLab account.