GitLab EE on AKS installed from chart won't start: Missing setting

Infrastructure as Code & Cloud Native
1

I’m trying to install GitLab EE using the official Helm chart (Files · master · GitLab.org / charts / GitLab Chart · GitLab) on AKS using Azure Blob Storage for keeping backups (Azure MinIO Gateway | GitLab).

When deploying, containers reading the generated gitlab.yml (gitlab-sidekiq-all-in-1, gitlab-unicorn) complain about a missing value:

$ kubectl logs gitlab-sidekiq-all-in-1-5fc87b76dc-nrttr -c dependencies
+ /scripts/set-config /var/opt/gitlab/templates /srv/gitlab/config
Begin parsing .erb files from /var/opt/gitlab/templates
Writing /srv/gitlab/config/gitlab.yml
Writing /srv/gitlab/config/database.yml
Writing /srv/gitlab/config/sidekiq_queues.yml
Writing /srv/gitlab/config/resque.yml
Copying other config files found in /var/opt/gitlab/templates
Copying smtp_settings.rb into /srv/gitlab/config
+ exec /scripts/wait-for-deps
Checking database connection and schema version
WARNING: This version of GitLab depends on gitlab-shell 9.3.0, but you're running Unknown. Please update gitlab-shell.
rake aborted!
Settingslogic::MissingSetting: Missing setting 'connection' in 'backup' section in /srv/gitlab/config/gitlab.yml
/srv/gitlab/vendor/bundle/ruby/2.6.0/gems/settingslogic-2.0.9/lib/settingslogic.rb:189:in `missing_key'
(eval):3:in `connection'
...

I’m using the following values.yaml to deploy:

## Find all the gory details at https://gitlab.com/charts/gitlab/blob/master/doc/installation/deployment.md
global:
  # Configuration for backups to azure using minio gateway
  # For further info check https://docs.gitlab.com/charts/advanced/external-object-storage/azure-minio-gateway.html
  minio:
    enabled: false
  appConfig:
    lfs:
      enabled: false
    artifacts:
      enabled: false
    uploads:
      enabled: false
    packages:
      enabled: false
    externalDiffs:
      enabled: false
    backups:
      bucket: backup-storage
      tmpBucket: tmp-storage
  initialRootPassword:
    secret: gitlab-gitlab-initial-root-password
    key: password
  hosts:
    domain: onesaitplatform.com
    hostSuffix: ssdd
    https: false
#    externalIP: 10.0.0.0
  smtp:
    enabled: true
    address: webmail.indra.es
    port: 2525
    user_name: onesaitdevops
    password:
      secret: gitlab-smtp-password # https://gitlab.com/charts/gitlab/blob/master/doc/installation/secrets.md#smtp-password
      key: password
    email:
      from: onesaitdevops@minsait.com
      display_name: Minsait
      reply_to: onesaitdevops@minsait.com
      subject_suffix: " | Minsait"
  ingress:
    enabled: false
    https: false
  registry:
    enabled: false
  tls:
    enabled: false
gitlab:
  gitaly:
    persistence:
      storageClass: default
      size: 10Gi
  task-runner:
    backups:
      objectStorage:
        backend: s3
        config:
          secret: backup-storage-config
          key: config
postgresql:
  persistence:
    storageClass: default
    size: 5Gi
minio:
  # enabled: false  This was moved to global section above
  persistence:
    storageClass: default
    size: 5Gi
registry:
  enabled: false
  storage:
    secret: registry-storage-config
    key: config
redis:
  persistence:
    storageClass: default
    size: 5Gi
certmanager-issuer:
  email: onesaitdevops@minsait.com
2

Checking the template used to generate gitlab.yml, I find the setting the pods complain about is missing:

$ kubectl describe configmap gitlab-sidekiq
...
gitlab.yml.erb:
----
production: &base
  ...
  backup:
    path: "tmp/backups"   # Relative paths are relative to Rails.root (default: tmp/backups/)
  gitlab_shell:
    path: /home/git/gitlab-shell/
  ...
...