Skip to content

feat(site-workflows): label sensor-created workflows with the event object - #2645

Merged
cardoe merged 1 commit into
mainfrom
workflow-object-labels
Nov 6, 2026
Merged

cardoe merged 1 commit into
mainfrom
workflow-object-labels

Conversation

@cardoe

@cardoe cardoe commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Sensors now add labels to the Workflows they submit, taken from the decoded oslo message: node, port, portgroup, instance, project, segment-range, and event-type (which apply varies per sensor).
  • Makes it easy to find workflows for a given object, e.g. kubectl -n argo-events get workflows -l node=<uuid>.

Notes

  • Plain label keys (no domain prefix) were used to avoid dot-escaping in dest paths.
  • Workflows submitted manually (argo submit) are not labelled.

…bject

Add labels (node, port, portgroup, instance, project, segment-range,
event-type) to the Workflows that sensors submit, taken from the decoded
oslo message. This makes it easy to find the workflows that ran for a
given object, e.g.:

  kubectl -n argo-events get workflows -l node=<uuid>
@cardoe
cardoe force-pushed the workflow-object-labels branch from ba9970e to 404a7c7 Compare November 6, 2026 18:07
@cardoe
cardoe enabled auto-merge November 6, 2026 18:10
@cardoe
cardoe added this pull request to the merge queue Nov 6, 2026
Merged via the queue into main with commit 07a94da Nov 6, 2026
20 checks passed
@cardoe
cardoe deleted the workflow-object-labels branch November 6, 2026 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants