Hi all! Looking for some clarification with respect to using the Helm chart, an external Postgres instance, and Kubernetes secrets. I have read through this, and understand that there needs to be (either generated by the Helm chart or not) a secret for the Postgres password. I have been generating the secret using the Helm chart, but now I don't want to do that. I believe that means I set:

generatePostgresqlPasswordSecret: false

So, do I still need to set these? Because the secret only stores the password. I don't want to set these here, I want all of this to be pulled from Kubernetes secrets.

postgresql:
  enabled: false
  postgresqlHost: "postgresqlHost"
  postgresqlUsername: "postgresqlUsername"
  postgresqlPassword: "postgresqlPassword"
  postgresqlDatabase: "postgresqlDatabase"
  service:
    port: 5432

If I don't set these, I don't see how the pieces that need to talk to Postgres would be able to. Is there any way to point to postgres without writing this all in the Helm chart?

i'm not expert in the helm chart but @rex @johann will probably know the right answer here

Hey @raaid, unfortunately we don’t provide support for this out of the box. As you’ve seen, we only provide configuration to optionally source the postgresql password from a Kubernetes secret, but the other configuration (host, username, database, service) has to be specified in the values.yaml.

you can use env variables though right?

In the Helm chart’s

dagster.yaml

, only the postgres password is sourced from env variable (which is in turn sourced by the kubernetes secret). The other configuration is directly templated from the

values.yaml

Dang okay that's what I was circling, thank you for the confirmation. That's all good, I've got a workaround one level up using Pulumi and Helm haha. Thanks for the responses, love using this tool and appreciate this Slack space a whole lot 🙂