In GitLab Self-Managed, how do the Linux package, the GitLab Helm chart and cloud native hybrid differ in where PostgreSQL, Redis and Gitaly run?
answer
- one package versus many pods
- where state is allowed to live
- the chart's version is not GitLab's
- a Gitaly pod serves alone
basics
~20 sThe Linux package installs GitLab with PostgreSQL, Redis and Gitaly on virtual machines. The Helm chart runs GitLab in Kubernetes but needs PostgreSQL, Redis and object storage outside the cluster; cloud native hybrid also keeps Gitaly on virtual machines.
solid answer
~40 sThe **Linux package** (formerly Omnibus) is one `deb` or `rpm` that bundles GitLab with PostgreSQL, Redis, Sidekiq and Gitaly; you configure each node in `/etc/gitlab/gitlab.rb`, apply it with `gitlab-ctl reconfigure`, and scale out by enabling different components on different VMs. The **GitLab Helm chart** deploys cloud native container images to Kubernetes, and its version is not GitLab's: chart 10.4.1 ships GitLab 19.4.1. Since GitLab 19.0 the chart no longer bundles PostgreSQL, Redis or object storage, so all three must be external. Gitaly can run in the cluster only as sharded, non-clustered Gitaly (generally available since 18.11), each pod a single point of failure for its repositories. **Cloud native hybrid** runs the stateless parts (Rails, Sidekiq) in Kubernetes and keeps Gitaly, including Gitaly Cluster, plus PostgreSQL and Redis on Linux package VMs or managed services.
code
yaml · 21 linesglobal:
hosts:
domain: example.com
psql:
host: psql.example.com
password:
secret: gitlab-postgresql-password
key: postgres-password
redis:
host: redis.example.com
auth:
secret: gitlab-redis
key: redis-password
gitaly:
enabled: false
external:
- name: default
hostname: praefect.example.com
port: 2305
authToken:
secret: external-gitaly-tokengo deeper
Recall that the Linux package installs everything on servers, while the Helm chart runs GitLab in Kubernetes and needs its database and Redis outside the cluster.
Explain where each stateful component may live in the three layouts, why the chart's version differs from GitLab's, and what changed for bundled services in 19.0.
Show why Gitaly is the deciding component: pod rotation versus graceful reload, sharded-only Gitaly in the cluster, and hybrid when repositories need automatic failover.
Decide whether Kubernetes skills, Gitaly availability needs and the extra resource cost justify the chart over the Linux package for this organisation.
## The Linux package: one package, many roles The **Linux package** (still called Omnibus in older material) is a single `deb` or `rpm` containing GitLab and the components it depends on: PostgreSQL, Redis, Sidekiq, Gitaly and the web front end. GitLab's documentation calls it the most mature installation method and notes that GitLab.com uses it too. - Every node is configured in `/etc/gitlab/gitlab.rb` and brought to that state with `sudo gitlab-ctl reconfigure`. - A single node runs everything. A multi-node install uses the same package on every VM and switches components on or off per node (`postgresql['enable']`, `gitaly['enable']`, and so on). - The reference architectures from 1,000 to 50,000 users are written for it, including the high-availability ones. ## The Helm chart: GitLab as Kubernetes workloads The **GitLab Helm chart** deploys GitLab's cloud native container images as Kubernetes workloads: web service and Sidekiq as autoscaling deployments, Gitaly as a StatefulSet, plus supporting pods. Two facts trip people up: - **The chart has its own version.** Chart 10.4.1 maps to GitLab 19.4.1; breaking chart changes can happen independently of GitLab. - **State lives outside.** The chart requires external PostgreSQL, Redis and object storage. Bundled PostgreSQL, Redis and object-storage charts were only ever meant for proof-of-concept use and were removed in GitLab 19.0 (chart 10.0); an instance still using them must migrate before that upgrade. The **GitLab Operator** is a further route onto Kubernetes: it manages the same cloud native images following the Kubernetes operator pattern and automates GitLab's upgrade steps. GitLab's installation-methods page adds the cost side for both: administration needs Kubernetes knowledge, and the default chart installation needs more resources than a single-node Linux package because most services are deployed redundantly. ## Where state may live | Component | Linux package | Cloud Native (all on Kubernetes) | Cloud native hybrid | |---|---|---|---| | Rails web, Sidekiq | VMs | Pods | Pods | | PostgreSQL | Bundled, or external | External or managed service | VMs or managed service | | Redis | Bundled, or external | External or managed service | VMs or managed service | | Object storage | Local or external | External | External | | Gitaly | VMs, sharded or Gitaly Cluster | StatefulSet pods, sharded only | VMs, sharded or Gitaly Cluster | ## Why Gitaly is the hard part **Gitaly** stores the Git repositories. Non-clustered Gitaly serves each repository from one node, so that node is a single point of failure for its repositories. - On a VM, the Linux package hides most of that during upgrades: it replaces the Gitaly binary in place and performs a **graceful reload**. - In Kubernetes a pod rotates by shutting down completely and starting a new pod, so an upgrade, a node drain or an eviction interrupts the repositories that pod serves; client retries soften it. - Gitaly on Kubernetes became **generally available in GitLab 18.11**, for sharded, non-clustered Gitaly only. **Gitaly Cluster (Praefect) on Kubernetes** was introduced as a **beta in 19.1** and is not part of the Cloud Native reference architecture. ## Choosing between them 1. **No Kubernetes, or no team that runs it well:** the Linux package on VMs, sized from a reference architecture. 2. **Kubernetes in-house and no need for repository-level failover:** GitLab 19.4's documentation recommends the **Cloud Native** architecture for new deployments, with every GitLab component in the cluster and PostgreSQL, Redis and object storage outside. 3. **Kubernetes in-house and Gitaly must fail over automatically:** **cloud native hybrid**, with the stateless components in the cluster and Gitaly Cluster on Linux package VMs. The Helm-specific mechanics (values files, releases, rollbacks) belong to Helm itself; what matters here is which GitLab component may live where. ```yaml global: gitaly: enabled: false external: - name: default hostname: praefect.example.com port: 2305 ``` That fragment is how a hybrid install points the chart at a Gitaly Cluster on VMs: the chart's own Gitaly is disabled and the external service, reached through Praefect on port 2305, must be named `default`.
- A team runs GitLab from the Helm chart with the bundled PostgreSQL and Redis. What blocks its upgrade to GitLab 19.0?GitLab 19.0 (chart 10.0) removed the bundled PostgreSQL, Redis and object-storage charts with no replacement; they were meant for proof-of-concept use only. Before upgrading, the team must migrate to external PostgreSQL, Redis and object storage, following the chart's bundled-chart migration guide.
- Why does Gitaly on Kubernetes cause interruptions that the same Gitaly on a VM avoids during upgrades?On a VM the Linux package swaps the Gitaly binary in place and gracefully reloads it. In Kubernetes the pod must shut down and a new one start, and non-clustered Gitaly serves each repository from that one pod, so its repositories are briefly unavailable; client retries soften it.
- How do you tell which GitLab version a given Helm chart release installs?Read the chart's version mappings, or list chart versions with Helm. The chart is versioned independently of GitLab, so chart 10.4.1 ships GitLab 19.4.1, and a breaking chart change can arrive without a GitLab major release.
- The Helm chart's major version equals GitLab's major version
- Run production PostgreSQL inside the cluster with the chart's bundled database
- Gitaly on Kubernetes gives automatic repository failover
- Cloud native hybrid puts every GitLab component, Gitaly included, in Kubernetes
- The Linux package cannot scale beyond a single server
Assumes GitLab 19.4 with Helm chart 10.4: the chart dropped its bundled PostgreSQL, Redis and object storage in 19.0, Gitaly on Kubernetes became generally available in 18.11, and Gitaly Cluster on Kubernetes has been beta since 19.1.