Deployment ignores gitlab.migrations.initialRootPassword

Summary

The helm deployment ignores gitlab-initial-root-password secret.

Steps to reproduce

Create a custom secret and deploy a new helm release (version 6.10.2) with modified initRootPassword-values. The custom secret is ignored, and an additional default secret gets created.

Configuration used

Create a custom secret:

apiVersion: v1
kind: Secret
metadata:
  name: demo-gitlab-initial-root-password
stringData:
  password: gitlabDemo42

Override the initialRootPassword with a values-file as documented:

gitlab:
  migrations:
    initialRootPassword:
      key: password
      secret: demo-gitlab-initial-root-password

Create the helm release:

helm install gitlab gitlab/gitlab --version 6.10.2 -n gitlab -f gitlab/values.yaml

Current behavior

The custom secret is ignored, and an additional default secret gets created.

$ kg secrets -n gitlab | grep root
demo-gitlab-initial-root-password     Opaque               1      16m
gitlab-gitlab-initial-root-password   Opaque               1      16m

Expected behavior

The custom secret is used and the root-login is working with this custom password.

Versions

• Chart: 6.10.2
• Platform:
  • Self-hosted: Microk8s
• Kubernetes: (kubectl version)
  • Client: v1.26.3
  • Server: v1.26.3
• Helm: (helm version)
  • Client: v3.10.1
  • Server: v3.10.1