https://dagster.io/ logo
Title
c

Caio Tavares

09/20/2022, 2:57 PM
hey all! I am new to dagster and trying to understand something that should be simple but I can't figure out how to automate that. We are running dagster on k8s deploying the official helm chart. The core components are in the namespace
dagster
. All of our pipelines/jobs should run on specific namespaces rather than the dagster one. How do I configure the configMap
user-env
to be deployed and created within each namespace where the jobs must run? What is happening is that once I trigger a pipeline, the job attempts to start on the target namespace but then I get an error:
configmap "xxx-dagster-dagster-user-deployments-yyy-user-env" not found: CreateContainerConfigErro
d

daniel

09/20/2022, 3:20 PM
Hi Caio - I don't think the helm chart automatically provisions that configmap for you in other namespaces. One option would be to set includeConfigInLaunchedRuns: false here for your user code deployments, which will make the run launcher stop including that -user-env configmap: https://docs.dagster.io/deployment/guides/kubernetes/deploying-with-helm#configure-your-user-deployment (this will only work if you're not setting env vars in your user code deployments that you then expect to be available when you launch runs) Another would to manually copy it over into the namespaces that you're planning to launch runs in.
I'm not sure if Helm supports installing resources in multiple namespaces for you - I'd have to check
c

Caio Tavares

09/20/2022, 4:05 PM
Thank you for the response @daniel. We are not passing any custom env variables to the user code deployments at the moment, so if we disable the includeConfigInLaunchedRuns then I might have an option? What about the postgres secret and pipeline-env required for the dagster job?
d

daniel

09/20/2022, 4:06 PM
I think you would need to add those in the namespaces where you want the runs to happen unfortunately 😕
c

Caio Tavares

09/20/2022, 4:08 PM
I see so I think I'd have to customize the helm chart in order to render the configmaps/secrets for each namespace. We want to have this automated so we can deploy Dagster with ArgoCD
d

daniel

09/20/2022, 4:08 PM
If you have an example of what those customizations look like, we could see about bringing them back upstream into the main helm chart
c

Caio Tavares

09/20/2022, 4:09 PM
Sounds good, I will think about a more general approach to achieve this and could open a PR