Replies: 2 comments 3 replies
-
Use
See https://github.com/argoproj/argo-workflows/blob/master/docs/environment-variables.md for details. |
Beta Was this translation helpful? Give feedback.
3 replies
This comment was marked as spam.
This comment was marked as spam.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear Argo community, is there currently an option to have the Argo generated pod names include the actual task/step name instead of the task template name?
So something like [workflow id]-[task name]-[random numeric string] instead of [workflow id]-[task template]-[random numeric string]
The reason for this is that very often we would run several similar tasks based on one single template, and we would use the actual task name to indicate the parameter. Using the task name instead of the template name makes it even easier to identify the right pods for troubleshooting.
For example - I might have a task template "process" which is referenced in two tasks "process-a" and "process-b", which these two tasks only differing in a few input parameters. Currently we can't directly tell which pod corresponds to process-a and which corresponds to process-b.
Thank you for your help!
Beta Was this translation helpful? Give feedback.
All reactions