Hi dagstermates! I have a problem. I set up

jobNamespace

to

dagster-jobs

in

runLauncher

, but my jobs still start in default namespace. Is there any ideas how to fix this? Probably i should restart something or edit configmap directly?

Hi mark - it’s probably pulling the namespace from your user code deployments and overriding the namespace that’s set on the run launcher. Is changing the namespace of the user code deployments too an option or do you want them to be separate?

I want to separate deployments(dagit, daemon, user-deployments) and jobs. Can you say where can I specify job namespace in user-deployment?

Ah hm, I may have misremembered the details of how this works, it doesn't look like there's way to customize the namespace for the user code deployments. If you set

includeConfigInLaunchedRuns.enabled

to

false

for your user code deployments it should stop copying over the namespace into your launched runs (but will also stop copying over things like secrets/volumes/etc.)

Wow, thank you very much! I thought it is only about resources.