GitLab Helm subcharts

The GitLab Helm chart is made up of multiple subcharts, which provide the core GitLab components:

• Gitaly
• GitLab Exporter
• GitLab Pages
• GitLab Runner
• GitLab Shell
• GitLab agent server (KAS)
• Mailroom
• Migrations
• Praefect
• Sidekiq
• Spamcheck
• Toolbox
• Webservice

The parameters for each subchart must be under the gitlab key. For example, GitLab Shell parameters would be similar to:

gitlab:
  gitlab-shell:
    ...

Use these charts for optional dependencies:

• MinIO
• NGINX
• HAProxy
• PostgreSQL
• Redis
• Registry
• Traefik

Use these charts as optional additions:

• Prometheus
• Unprivileged GitLab Runner that uses the Kubernetes executor
• Automatically provisioned SSL from Let’s Encrypt, which uses Jetstack’s cert-manager with certmanager-issuer

GitLab Helm subchart optional parameters

affinity

affinity is an optional parameter in all GitLab Helm subcharts. When you set it, it takes precedence over the global affinity value. For more information about affinity, see the relevant Kubernetes documentation.

With affinity, you can set either or both:

• podAntiAffinity rules to:
  • Not schedule pods in the same domain as the pods that match the expression corresponding to the topology key.
  • Set two modes of podAntiAffinity rules: required (requiredDuringSchedulingIgnoredDuringExecution) and preferred (preferredDuringSchedulingIgnoredDuringExecution). Using the variable antiAffinity in values.yaml, set the setting to soft so that the preferred mode is applied or set it to hard so that the required mode is applied.
• nodeAffinity rules to:
  • Schedule pods to nodes that belong to a specific zone or zones.
  • Set two modes of nodeAffinity rules: required (requiredDuringSchedulingIgnoredDuringExecution) and preferred (preferredDuringSchedulingIgnoredDuringExecution). When set to soft, the preferred mode is applied. When set to hard, the required mode is applied. This rule is implemented only for the registry chart and the gitlab chart alongwith all its subcharts except webservice and sidekiq.

nodeAffinity only implements the In operator.

The following example sets affinity, with both nodeAffinity and antiAffinity set to hard:

nodeAffinity: "hard"
antiAffinity: "hard"
affinity:
  nodeAffinity:
    key: "test.com/zone"
    values:
    - us-east1-a
    - us-east1-b
  podAntiAffinity:
    topologyKey: "test.com/hostname"