[bitnami/postgresql-ha] Pgpool connecting without password even provided password in values.yaml file

[venkatne]

Name and Version

bitnami/postgresql-ha-14.2.3

What architecture are you using?

amd64

What steps will reproduce the bug?

Deploy postgresha solution with below values and deploy with command helm install -f values.yaml postgresql bitnami/postgresql-ha -n psql

global:
  imageRegistry: ""
  ## E.g.
  ## imagePullSecrets:
  ##   - myRegistryKeySecretName
  ##
  imagePullSecrets: []
  storageClass: ""
  postgresql:
    username: "postgres"
    password: "test1234"
    database: ""
    repmgrUsername: "postgres"
    repmgrPassword: "test1234"
    repmgrDatabase: ""
    existingSecret: ""
  ldap:
    bindpw: ""
    existingSecret: ""
  pgpool:
    adminUsername: "postgres"
    adminPassword: "test1234"
    existingSecret: ""

### Are you using any custom parameters or values?

Yes here is values file 

  postgresql:
    username: "postgres"
    password: "test1234"
    database: ""
    repmgrUsername: "postgres"
    repmgrPassword: "test1234"
    repmgrDatabase: ""
    existingSecret: ""
  ldap:
    bindpw: ""
    existingSecret: ""
  pgpool:
    adminUsername: "postgres"
    adminPassword: "test1234"
    existingSecret: ""

What is the expected behavior?

Service postgresql-postgresql-ha-pgpool should only connect with password test1234 provided in values.yaml but it is connecting with out password authentication

What do you see instead?

Service postgresql-postgresql-ha-pgpool should only connect with password test1234 provided in values.yaml but it is connecting with out password authentication

Additional information

If I deploy with providing values.yaml I see it is working fine, I mean if deployed helm install postgresql bitnami/postgresql-ha -n psql which is working as expected(only able to connect with password generated automatically)

[rafariossaa]

Hi,
Sorry for the long delay.
Could you check version >= 14.2.5 ? We fixed a related issue in that version.

[github-actions]

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.

[venkatne]

Even with 14.2.7 we still see the same issue!

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.

[venkatne]

I am seeing the issue with latest release also!

[Nickmman]

Hi @rafariossaa Can you please reopen this? Running 14.2.7, the issue is still present:

postgres@tmp-shell:/$ psql -h postgresql-ha-pgpool -U postgres postgres
psql (16.3)
Type "help" for help.

postgres=# \q
postgres@tmp-shell:/$ psql -h postgresql-ha-postgresql -U postgres postgres
Password for user postgres:
psql (16.3)
Type "help" for help.

postgres=# \q
postgres@tmp-shell:/$

[fmulero]

Please amend me if I am wrong but It seems a consequence of using the same admin user and password for postgresql and the replication manager, which is not a good practice.

[Nickmman]

Please amend me if I am wrong but It seems a consequence of using the same admin user and password for postgresql and the replication manager, which is not a good practice.

That does seem to be the case in this scenario, I just tested with a new deployment having individual usernames and passwords for each purpose and I get asked for a password for each test, both in the pgpool service and the regular postgresql service.

Given this information, I think the original issue can be closed.