Hey Team this might be more of a helm question I noticed tha

Question

Hey Team this might be more of a helm question I noticed that in the user deployments there is a shared config map created called `` lt name gt user deployments shared env` can anyone give examples of how one would append to this in order to establish common environment variables Wasn t seeing anything in the documentation of how to do this let alone it even being a thing

daniel · Answer

I don t think we have a hook for adding these to all user code deployments but we do have one for setting env vars for individual deployments <https github com dagster io dagster blob master helm dagster charts dagster user deployments values yaml L73 L82>

Scott Hood · Answer

Yep I saw this one I have already currently built out a config map and applied to our first deployment however after seeing that there was a config map being created wondering if I can abstract that process away by appending onto the one user deployments creates Also simply curious about how one adds to config maps if say for example you have secrets being pulled from external secret managers

daniel · Answer

the `env ` field that i linked also makes a config map for you it s just scoped to the individual deployment rather than shared across all of them

Scott Hood · Answer

Yep which generates this guy ` lt chatname gt lt deploymetn name gt user env` Problem with this is we will have multiple deployments and have a set of common environment variables that we want applied to each so either we have to create a config map once apply it to every deployment or like you have here apply the environment variables to each deployment

daniel · Answer

I ll file an issue for that seems like a very reasonable request

daniel · Answer

< Dagster Bot> issue in the Helm chart allow a way to set shared environment variables that apply to all user code deployments

Dagster Bot · Answer

Created issue at <https github com dagster io dagster issues 7747>

Scott Hood · Answer

I think I found this <https github com dagster io dagster commit 9941f61fabf574871e4896c5cbb1a7c21c1ed9f3> Which indicates that the value might be `dagsterUserDeployments sharedEnv` for setting the global confits

daniel · Answer

`dagsterUserDeployments sharedEnv` is an internal function for our helm chart it s not something that we expose directly in the values yaml unfortunately

daniel · Answer

for now i think the best workaround we have is to create your own configmap with the shared env vars you want and reference that configmap in the envConfigMaps for each of your deployments

Scott Hood · Answer

Sounds good thanks

Scott Hood · Answer

Hey < daniel> does Dagsters env variable take in secrets normally We are trying to set `AzureKeyVaultSecret` to the env list via ``` env name AUTH TOKEN valueFrom secretKeyRef name lt secret name gt key lt dataKey gt ``` However was apparently running into errors Our AKS group is saying to simply set the `envSecrets` however not sure based on that how its supposed to route the dataKey to the correct Environment variable name

daniel · Answer

I think you want envSecrets yeah That will mount all the env vars in that secret like in the secretRef example here <https kubernetes io docs concepts configuration secret use case as container environment variables>

daniel · Answer

it assumes the keys in the secret data are the same as the env var names

Scott Hood · Answer

Does it turn the dataKey into proper env format or does it just take the name straight up

daniel · Answer

what do you mean exactly by proper env format

daniel · Answer

UPPER CASE WITH UNDERSCORES

daniel · Answer

it just takes the name straight up to answer your question

Scott Hood · Answer

Ok I see so just make the dataKey the value of the env

daniel · Answer

Yeah the key is the env var name and the value is the env var value