The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

I searched around but couldn’t find an answer, but is the Kubernetes run worker job name customizable? It looks like K8s Job Name is `dagster-run` as a prefix with the Run ID as the suffix. Would be nice to add the job name, a timestamp, etc, if possible.  Thanks

funny, I was about to ask the same question today

seems like only the job's `run_id` is considered when building the job name. <https://github.com/dagster-io/dagster/blob/08771c5662b3002d58e00ded0eea0f9b0f429b67/python_modules/libraries/dagster-k8s/dagster_k8s/launcher.py#L270|see code>

We do label the Jobs with `dagster/job`, so the info is there but not as available. There is a length limit and some other restrictions on the naming, so it’d be a balance including job name and timestamp and run id etc.
Feel free to submit an issue but I think it’s likely not something we’ll be able to immediately prioritize. Run launchers are very pluggable though, so you could always write a custom launcher extending ours

thanks <@U015C9U9RLK> the label is super useful. I'm trying to see job names on datadog's built-in K8s Jobs dashboard

according to <https://docs.datadoghq.com/containers/kubernetes/tag/?tab=containerizedagent#pod-labels-as-tags|datadog docs> I can get the agent to set the job_name label as a tag, then I can use it in dashboards :sweat_smile: