Kubeflow Pipelines + Argo Workflows: WorkflowTemplate API Adoption for Reusable Steps

Migration Strategy for WorkflowTemplate Adoption

The operator does not currently support the WorkflowTemplate CRD, meaning a direct, zero-downtime migration path that automatically converts existing legacy Workflow CRDs to WorkflowTemplate CRDs while preserving historical runs is not available through the Kubeflow Pipelines operator itself.

Confirmed Facts vs. Assumptions

• Confirmed Fact: Kubeflow Pipelines currently relies on legacy Workflow CRDs, even when running Argo Workflows v3.5+ (which supports WorkflowTemplate).
• Confirmed Fact: Adopting WorkflowTemplate offers significant benefits in step reusability and versioning.
• Assumption: The existing pipeline runs, defined via legacy Workflow specs, must continue to execute successfully using the current operator version.

Required Steps for Adoption

1. Maintain existing pipeline definitions using the legacy Workflow CRD to ensure backward compatibility for current and historical runs.
2. Develop new, reusable steps using the WorkflowTemplate API in parallel.
3. Update pipeline definitions incrementally, replacing specific, duplicated step logic with references to the new, versioned WorkflowTemplate definitions.

This phased approach isolates the risk: new workflows benefit from WorkflowTemplate, while existing ones remain functional under the legacy spec.

Diagnostic Requirement

To provide a more precise migration timeline, please confirm the exact version of the Kubeflow Pipelines operator deployed in the cluster, as operator feature parity is the determining factor for native WorkflowTemplate support.