Helm/K8s deploy question: Is it possible to change the namespace in the

CeleryK8sRunLauncher

? I am getting 403 errors when attempting to run jobs and it appears it’s trying to create jobs in the

default

namespace.

Hey Dusty - the way that picks up the namespace is a bit strange right now compared to our other launchers (the celery-k8s launcher could use a bit of a refresh to be brought in line with the vanilla k8s run launcher). I believe it pulls the namespace from config on the executor actually. So you can have config on your run like

"execution": {
            "config": {"job_namespace": YOUR_NAMESPACE_HERE}
       }

and then that namespace should be used for both the launched runs and the pods for the individual steps

Ok, and to be clear, this is not a K8s config, this is code that’s part of the user DAG code?

Yeah, that's run config, like what you would put on a job or put in the YAML editor in the launchpad

Got it. Admittedly I haven’t developed any DAG code yet, I was just deploying using the example DAG code provided via Docker repo in the docs, but will keep this in mind when I do start to deploy our own DAG code. Thanks Daniel!

I think it has to be job-level unfortunately