pgbouncer add `authPassword` through a secret

[matthew-hull-bright]

It would be very useful to provide a name of a secret, and a key in the secret to use as the authPassword please. Am I missing something?

helm/charts/pgbouncer/values.yaml

Line 174 in 00f890a

authPassword:

[masterkain]

this is already possible with the current chart, but the supported path is config.existingUserlistSecret, not a dedicated authPassword secret ref

right now config.authPassword is only used when the chart generates userlist.txt for you

if you want to keep the password out of values, you can provide your own Secret containing the full userlist.txt and set:

config:
  adminUser: admin
  authUser: auth_user
  existingUserlistSecret: my-pgbouncer-userlist

with a Secret like:

apiVersion: v1
kind: Secret
metadata:
  name: my-pgbouncer-userlist
type: Opaque
stringData:
  userlist.txt: |
    "admin" "supersecret-admin-password"
    "auth_user" "supersecret-auth-password"

so the deployment outcome is already supported today

what is not currently supported is a narrower values API like "keep chart-managed userlist generation, but read only config.authPassword from secretName/key"

if that convenience would still be useful, we can keep this issue open as an enhancement for a more granular secret-ref interface

[matthew-hull-bright]

First thank you for the awesome reply.

With your steer I got it working (I tested the limits a bit at first, for example trying without existingAdminSecret as it felt like duplication having a secret for that and having another for the user list but it threw errors with the missing admin password key so had to put back in).

Thanks again for the support, in return if I can help by tweaking the docs to save others struggling with the same would be happy to do so.

I don't see the need for the enhancement at this time but again thank you for suggesting.