19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
With regards to the k8s executor and user deployme...
# ask-communityr
Ryan Riopelle
05/12/2023, 5:06 PMWith regards to the k8s executor and user deployments, is there a way to change the run pod/job names from "dagster-run-xxx" to a name that would help a user determine which user deployment that pod is coming from?
🤖 1
j
johann
05/12/2023, 6:13 PMThere’s not. Would a k8s label suffice? We could stick code location name in with job name here https://github.com/dagster-io/dagster/blob/master/python_modules/libraries/dagster-k8s/dagster_k8s/launcher.py#L228
r
Ryan Riopelle
05/12/2023, 6:23 PMThat might be good to add, but it will still be hard to tell which pod is running what job just looking at pods
j
johann
05/12/2023, 6:26 PMWhat interface are you using for that?
kubectl get podsr
Ryan Riopelle
05/12/2023, 6:30 PMk9s, lense
Ryan Riopelle
05/12/2023, 6:30 PMcurrently don't have lense running, not sure if there is a good way to use that to filter by tags
j
johann
05/12/2023, 6:33 PMWould you mind filing an issue for this?
johann
05/12/2023, 6:34 PMI don’t think we’ll be able to get to it immediately. We do take pr’s though 🙂