Hello I need help to setup dagster on Kubernetes with extern

Question

Hello I need help to setup dagster on Kubernetes with external postgresql I am a bit lost dagster will be a subchart of my chart one subchart is to setup postgresql differently in this K8s instance Unfortunately Scretes structure are different and I am lost of how to setup cleanly the values yaml To setup the external database I have this to setup the subchart named postgresql ```postgresql parameters DATABASE SERVICE NAME postgresql service POSTGRESQL DATABASE somepgdatabase POSTGRESQL PASSWORD test POSTGRESQL USER test``` this creates secrets with those keys ```database name database password database user``` For the subchart of dagster I have this ```dagster postgresql set postgresql enabled to be false to disable deploy of a PostgreSQL database and use an existing external PostgreSQL database enabled false Used by init container to check that db is running Even if enabled false image registry registry default svc 5000 repository repo postgresql tag latest pullPolicy IfNotPresent set this PostgreSQL hostname when using an external PostgreSQL database postgresqlHost postgresql postgresqlUsername test Note when changing this password e g in test that credentials will persist as long as the PVCs do see postgresqlPassword test postgresqlDatabase somepgdatabase set postgresql parameter keywords for the connection string see postgresqlParams service port 5432``` and finally ```global postgresqlSecretName postrgresql secret name ``` which seems to define configmap which points to the dagster secrets What I want if possible is that from a single secrets it is mapped to both env in subcharts is it possible

Thomas · Answer

In fact I wonder if the global value is needed for my case since I manage it outside dagster ``` Whether to generate a secret resource for the PostgreSQL password Useful if global postgresqlSecretName is managed outside of this helm chart generatePostgresqlPasswordSecret true```

rex · Answer

The docs on this are here <https docs dagster io deployment guides kubernetes customizing your deployment configuring an external database> I think in your case you would want ```global postgresqlSecretName database password generatePostgresqlPasswordSecret false```

Thomas · Answer

Unfortunately no disappointed the key is imposed to `postgresql password` and is not a variable See line 58 So I can change the secret name but I need to add another key duplicated in this secret to access the value Like done with Maybe I can ask for an enhancement

Thomas · Answer

I think dagster impose this because of the chart of postgresql

Thomas · Answer

rex · Answer

ah when you mentioned `database password` I thought it was the name of your secret Yes you re correct it s currently hard coded to read from the `postgresql password` key of whatever secret you pass to the helm chart

rex · Answer

feel free to file a feature request for this

Thomas · Answer

Ok I see 21 occurences with defaults I will look