-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Closed
Description
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!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels