Replies: 1 comment
-
100% agree on this on this allowing the ability to set the secret name (done) and secret key (todo) would give ultimate flexibility and is a pretty common pattern amongst other helm charts I have used. I am using cloud native-pg to spin up a database and it auto-genarates a secret with all the connection details (as below).
Introducing a new helm value |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For a variety of reasons, we have the password to an externally managed postgres instance that we want to point dagster at in a key that is not named
postgresql-password
. Can this be made a parameter in the helm chart? The workarounds we have now are:We can't even overrride the value with the
fromSecret
options that dagster provides because things set withenv
take precedence. What is the right way to do this?Beta Was this translation helpful? Give feedback.
All reactions