[bitnami/mariadb] Unable to upgrade without passing the rootPassword to values.yaml about charts HOT 5 CLOSED

That's expected. Since the password from the first deployment is stored in the volume and volumes are not recreated during upgrades, you need to follow those instructions to use the already set password.

from charts.

But the correct working password is already stored in the secret, why do I need to specify it as a plaintext in the values.yaml again? Why the chart can't just get it from the secret directly?

This problem persists even if I specify the secret for passwords explicitly like:

auth:
  existingSecret: "db-credentials"

from charts.

Hi @MurzNN

We already have mechanisms in place to detect there's an existing secret and reuse its data thanks to the use of the common.secrets.passwords.manage helper, see:

• https://github.com/bitnami/charts/blob/main/bitnami/mariadb/templates/secrets.yaml#L8

You can reproduce it following these steps:

• Install the chart setting a custom password for auth.rootPassword:

helm install mariadb oci://registry-1.docker.io/bitnamicharts/mariadb \
  --set auth.rootPassword=some-secret-password \
  --version 14.1.4 

• Ensure the password has been properly set:

$ kubectl get secret mariadb -o jsonpath='{.data.mariadb-root-password}' | base64 --decode
some-secret-password

• Upgrade the release without providing any password and double-check the secret data didn't change:

$ helm upgrade mariadb oci://registry-1.docker.io/bitnamicharts/mariadb --version 14.1.4
Pulled: registry-1.docker.io/bitnamicharts/mariadb:14.1.4
Digest: sha256:e8997dd398073d025d5ab076b89ca16e3f2eb08ad4c13d5ddd49ad795fc74c32
Release "mariadb" has been upgraded. Happy Helming!
NAME: mariadb
(...)
$ kubectl get secret mariadb -o jsonpath='{.data.mariadb-root-password}' | base64 --decode
some-secret-password

from charts.

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

from charts.

Yeah, all works well, sorry for bothering! The problem was that the secret file was created after the helm upgrade happened, because of this it was not detected and asked to specify the rootPassword.
After fixing the pipeline - all starts working well!

from charts.