-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Open
Description
Pre-requisites
- I have double-checked my configuration
- I have tested with the
:latestimage tag (i.e.quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on:latest. If not, I have explained why, in detail, in my description below. - I have searched existing issues and could not find a match for this bug
- I'd like to contribute the fix myself (see contributing guide)
What happened? What did you expect to happen?
In the Argo Workflows UI (Workflow List view), the nameFilter behaves correctly only on the initial load.
However, when the UI begins watching workflows via the watch (stream) API, new incoming workflows appear in the list even if they do not match the name filter.
This results in the UI displaying workflows that should be filtered out.
Version(s)
v3.6.2
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflow that uses private images.
Steps to Reproduce
- Open Argo Workflows UI → Workflows.
- Apply a name filter (e.g., my-prefix-).
- Confirm that the initially loaded workflows are filtered correctly.

- Trigger creation of new workflows that do not match the filter.

- Observe that these new workflows still appear in the list during streaming updates.### Expected Behavior
Only workflows that match nameFilter should appear — both on initial load and during watch/stream updates.
Actual Behavior
Workflows received via the watch stream are rendered even when their names do not satisfy the filter.
Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}
Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded
Metadata
Metadata
Assignees
Labels
No labels