How to run Workflow steps against multiple Kubernetes clusters?

[caatclaudia]

I’m trying to understand the correct and supported way to run workflows that can target multiple Kubernetes clusters from a single Argo Workflows installation.

Use case

I have Argo Workflows installed in one Kubernetes cluster (let’s call it cluster A). From a WorkflowTemplate running in cluster A, I want to:

• Create Kubernetes resources (e.g. Job, Deployment) in another Kubernetes cluster (cluster B)
• Or have specific steps in a workflow execute against different clusters dynamically
• Ideally select the target cluster per step/template

What I tried

I attempted a few approaches:

1. Using resource template with:

clusterName: dev-cluster

1. Configuring a kubeconfig secret mounted via controller config:

kubeConfig:
  secretName: argo-cluster-dev-kubeconfig-cluster
  secretKey: kubeconfig

However:

• clusterName gets silently removed from the WorkflowTemplate after submission
• The controller does not seem to log or recognize any “cluster routing”
• The behavior suggests this field is not supported in my current Argo version (or CRDs)

Questions

1. Is multi-cluster resource execution supported in Argo Workflows today?
2. If yes, what is the recommended pattern?

• per-cluster kubeconfig secrets?
• executor per cluster?
• Argo Events + remote submission?

3. Is clusterName actually a valid field in resource templates in any released version?
4. If not, is there a roadmap or design proposal for native cluster targeting?

Expected outcome

I would like to have a supported way to:

• Run a workflow in cluster A
• Execute some steps that create resources in cluster B
• Without manually running multiple Argo installations or external scripts

#MultiCluster

[sueun-dev]

this looks very close to #3523 and the older #3516. The useful bit is that both threads frame this as multi-cluster support work, not just a missing example for clusterName in a resource template.

I'd start with #3523 before treating this as a new Q&A. It has the history of the dev multi-cluster builds, OCM PoC discussion, and maintainer comments about the scope being a big feature. #3516 is also worth reading for the older single-cluster boundary.