Zack D.
06/01/2023, 8:35 PMk8sRunLauncher
, but we couldn't get it fully work. After the configuration, we got the ops running under the namespace with the pod name as dasgter-step-<uuid>
. However, the job pod is still running under the default namespace with the pod's name as dagster-run-<uuid>
. We have configured the execution config for the job to pass the job_namespace
attribute, and its value should be dynamic depending on which tenant we are using. Do you have any ideas if we have missed any other configuration? Below is our execution config:
execution:
config:
env_secrets:
- tenantX-secret
job_namespace: tenantX
ops:
op_1: ...
op_2: ...
daniel
06/01/2023, 8:42 PMdaniel
06/01/2023, 8:45 PMZack D.
06/04/2023, 7:10 PMUserDefinedDagsterK8sConfig
by passing the tag including namespace under the job_metadata
. I was expecting to see the namespace passing on the tag will overwrite the default namespace. However, when we launched the job, it shows unmatched error: HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the namespace of the provided object does not match the namespace sent on the request","reason":"BadRequest","code":400}.
I guess the job namespace might be coming from the helm charts setting where we configure the Launcher.
We are still looking for a way to configure the namespace for the dagster-run from the tag. Do you think there will be a release for Dagster having this feature?daniel
06/04/2023, 7:11 PMZack D.
06/04/2023, 7:14 PMKingshuk
11/07/2023, 12:44 PM