Hey all! I am running a job with the

k8s_job_executor

and each step of the job is being spawned as an own pod. I am running dagster version 0.14.20 In my job I set the

job_spec_config

to

{'ttl_seconds_after_finished': 120}

, and in the docs it says that jobs and their associated pods get deleted after the TTL has expired. After the TTL is exceeded, the k8s-job gets deleted, but my

dagster-step-<SOME_ID>

- pods are not. Is there some issues with the

k8s_job_executor

, that these pods are not associated with the job, and is there a way I can achieve this?

Ah the docs are a bit misleading. If you put the same job_spec_config in the tags of your ops I think it should work

thanks a lot! that works like a charm daggy love