Current behaviour
We currently have several Kubernetes pod labels to identify which runtime pods are belonging to which workflow:
- reana-run-dask-workflow-uuid
- reana-run-batch-workflow-uuid
- reana-run-job-workflow-uuid
When Kubernetes cluster admin would like to filter all pods "belonging" to a workflow, the admin needs to seach for all these label variants.
Expected behaviour
Since "workflow UUID" is a concept orthogonal to pods, we can consider harmonising on using workflow-uuid everywhere.
However, note that we rely on full label names in various watchers and logging agents, so beware doing such a change blindly. E.g. we may want not to replace existing label, but simply to add a new workflow-uuid label only.
Notes
This issue is a follow-up from #664.
Current behaviour
We currently have several Kubernetes pod labels to identify which runtime pods are belonging to which workflow:
When Kubernetes cluster admin would like to filter all pods "belonging" to a workflow, the admin needs to seach for all these label variants.
Expected behaviour
Since "workflow UUID" is a concept orthogonal to pods, we can consider harmonising on using
workflow-uuideverywhere.However, note that we rely on full label names in various watchers and logging agents, so beware doing such a change blindly. E.g. we may want not to replace existing label, but simply to add a new
workflow-uuidlabel only.Notes
This issue is a follow-up from #664.