Summary
When submitting a new workflow, the "Select a workflow template" dropdown currently renders
all templates in a single flat list. As the number of templates grows this becomes hard to
navigate, users must scroll through an unorganised list to find what they need.
This proposal adds support for grouping templates in that dropdown using a standard Kubernetes
label on the WorkflowTemplate resource:
workflows.argoproj.io/ui-group: <group-name>
Templates that share the same label value are grouped together under a bold section header.
Templates without the label fall into an "Other" catch-all group at the bottom.
When no templates carry the label the list renders exactly as it does today , fully backwards compatible.
Proposed dropdown behaviour
Use Cases
- Teams with many workflow templates across different domains (e.g. deployments, data pipelines,
infrastructure) want to find templates quickly without scrolling through a long flat list.
- Platform teams managing a shared Argo cluster for multiple product teams want to visually
separate templates per team without requiring separate Kubernetes namespaces.
- New users benefit from a labelled, structured list that signals which templates belong together.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
Summary
When submitting a new workflow, the "Select a workflow template" dropdown currently renders
all templates in a single flat list. As the number of templates grows this becomes hard to
navigate, users must scroll through an unorganised list to find what they need.
This proposal adds support for grouping templates in that dropdown using a standard Kubernetes
label on the
WorkflowTemplateresource:Templates that share the same label value are grouped together under a bold section header.
Templates without the label fall into an "Other" catch-all group at the bottom.
When no templates carry the label the list renders exactly as it does today , fully backwards compatible.
Proposed dropdown behaviour
Use Cases
infrastructure) want to find templates quickly without scrolling through a long flat list.
separate templates per team without requiring separate Kubernetes namespaces.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.