Closed manhhailua closed 4 years ago
Hi @manhhailua thanks for opening the issue,
We've checked the steps you have mentioned above but we weren't able to reproduce the issue. Could you check if you have already a PVC from a previous deployment and it is conflicting with the new password? Please, could you try to install it again from scratch?
$ kubectl delete pvc data-postgresql-01-postgresql-0
$ helm install postgresql-01 bitnami/postgresql --set postgresqlPassword=1qaz2wsx
These steps worked for me.
@dani8art Oops, my bad! Thank you! I deleted all the pvc using the Longhorn UI, It's worked now. As you said, the passwords conflicted somehow.
Which chart: bitnami/postgresql (9.3.3)
Describe the bug After a very normal installation of
postgresql
chart, I could not access the database with providedpostgresqlPassword
even if the providedpostgresqlPassword
value was correctly set to secret. The database can be authenticated if nopostgresqlPassword
is set (use auto generated password -sudo helm install postgresql-01 bitnami/postgresql
).To Reproduce Steps to reproduce the behavior:
sudo helm install postgresql-01 bitnami/postgresql --set postgresqlPassword=1qaz2wsx
export POSTGRES_PASSWORD=$(sudo kubectl get secret --namespace vindr-dev postgresql-01 -o jsonpath="{.data.postgresql-password}" | base64 --decode)
sudo kubectl run postgresql-01-client --rm --tty -i --restart='Never' --namespace vindr-dev --image docker.io/bitnami/postgresql:11.9.0-debian-10-r1 --env="PGPASSWORD=$POSTGRES_PASSWORD" --command -- psql --host postgresql-01 -U postgres -d postgres -p 5432
Expected behavior The databased should be authenticated.
Version of Helm and Kubernetes:
helm version
:kubectl version
:Additional context My kubernetes cluster is a K3S cluster with 1 master and 3 nodes,
traefik
disabled and usinglonghorn
storageclass.