Hello everyone, I’m relatively new to Dagster and ...
# deployment-kubernetes
Hello everyone, I’m relatively new to Dagster and I’m trying to use CeleryK8sRunLauncher. I can’t seem to find a parameter similar to runK8sConfig.podSpecConfig to set nodeSelector for jobs. Currently, my jobs are starting on all nodes, but I would like them to start on nodes where Dagster is deployed. Could you please help me with this?
Hi nikita - that field isn't currently available on the CeleryK8sRunLauncher, but setting these tags on the job should work: https://docs.dagster.io/deployment/guides/kubernetes/customizing-your-deployment#per-job-or-per-op-kubernetes-configuration If that instance-level field would be useful to you, you could file a github feature request issue
❤️ 1
thank you very much, we will try this approach
Hello again, Daniel. Can you please tell me where to specify the nodeSelector for
? The option provided in https://docs.dagster.io/deployment/guides/kubernetes/customizing-your-deployment#per-job-or-per-op-kubernetes-configuration only worked for
. I apologize if this is a silly question.
That would go in config on the dagster @job decorator like in the example (if it works for dagster-step-* that would be because it was on the op or asset, not the job)
Thank you, Daniel. This is very helpful to us in solving the problem.
condagster 1