WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

add workflow-uuid labels for user runtime pods #667

@tiborsimko

Description

@tiborsimko

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions