What is the ability of that thing? can it enable running workflow pods in remote cluster?

[levsa762]

argo-workflows/docs/workflow-controller-configmap.yaml

Lines 51 to 62 in 946a2d6

	# uncomment following lines if workflow controller runs in a different k8s cluster with the
	# workflow workloads, or needs to communicate with the k8s apiserver using an out-of-cluster
	# kubeconfig secret
	# kubeConfig:
	# # name of the kubeconfig secret, may not be empty when kubeConfig specified
	# secretName: kubeconfig-secret
	# # key of the kubeconfig secret, may not be empty when kubeConfig specified
	# secretKey: kubeconfig
	# # mounting path of the kubeconfig secret, default to /kube/config
	# mountPath: /kubeconfig/mount/path
	# # volume name when mounting the secret, default to kubeconfig
	# volumeName: kube-config-volume

I'm interested in running workflow pods in a different Kubernetes cluster. Does the kubeconfig section help facilitate that?
Additionally, I found some examples using a tool called Admiralty to enable remote cluster execution. Is that a recommended approach, or is there native support within Argo for this use case?
Thanks!

[MasonM]

I haven't used this feature, but yes, it should allow you to run workflow pods in a different cluster than the workflow controller. It was added in #1134 and is documented at https://argo-workflows.readthedocs.io/en/latest/workflow-controller-configmap/#kubeconfig

[levsa762]

Just filling out this section didn’t do anything for me — I only saw it in the configuration and that’s it. I’d like you to show a proper example of how to configure it so that pods actually run on a remote cluster. Please include the prerequisites and, if you used a third-party tool like Admiralty, explain how to configure it as well. There isn’t much documentation available on this topic.
Thank you !