Summary

Currently, the Argo Workflows UI allows filtering of Workflows using label selectors via query parameters in the URL (e.g.,
https://<host>/workflows?namespace=xyz&label=key%3Dvalue), which is very helpful for narrowing down views.

However, this feature does not work for WorkflowTemplates. When attempting to filter the WorkflowTemplates list using similar query parameters (e.g.,
https://<host>/workflow-templates?namespace=xyz&label=key%3Dvalue), the label filter is silently ignored, and the UI lists all available templates.

This is despite the fact that the API supports filtering WorkflowTemplates via label selectors, as demonstrated by a direct API call to:
/api/v1/workflow-templates/?listOptions.labelSelector=key%3Dvalue

This inconsistency:

• Limits the ability to create UI links that show only a subset of user-facing templates (e.g., hide internal or system templates).
• Breaks the symmetry with workflow filtering behavior.

Expected Behavior:

When visiting the WorkflowTemplates page with a label= query parameter, only the templates matching the label selector should be shown, just like it works for workflows.

Actual Behavior:

The label query parameter is ignored in the WorkflowTemplates UI, and all templates are displayed.

Proposed Fix:

Support label=<labelSelector> query parameters in the /workflow-templates UI route, and apply them consistently when rendering the list view.

Use Cases

Argo Workflows allows adding custom UI links (via workflow-controller-configmap). These links could point directly to filtered views of WorkflowTemplates, making it easier for users to launch workflows relevant to their context. However, since label filtering currently doesn't work for the /workflow-templates UI route, this use case is blocked.

Message from the maintainers:

Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.