Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run Steps on Remote Cluster #3696

Closed
hyorigo opened this issue Aug 7, 2020 · 4 comments
Closed

Run Steps on Remote Cluster #3696

hyorigo opened this issue Aug 7, 2020 · 4 comments
Labels
area/multi-cluster type/support User support issue - likely not a bug

Comments

@hyorigo
Copy link

hyorigo commented Aug 7, 2020

Summary

We want to figure out best/simplest practice to run steps on remote cluster.

Already read through and tried the admiraltyio/multicluster-scheduler solution, however it's kinda complicated and overwhelming for our scenarios:

Working with only Argo itself, is there any possible or solution to let argo-server of Argo on one cluster, and workflow-controller of Argo to create/watch step pods on the other cluster?

Motivation

We're building a specific CI/CD based on Argo, for some performance testing or test cases involving GPU nodes scenarios, the step pods should be running on the same remote cluster with the testbed pods. And we want to minimize the changes upon the remote clusters.

@alexec
Copy link
Contributor

alexec commented Aug 7, 2020

Argo Workflows is designed to be install into the cluster it is needed for. We do not currently support multi-cluster. See #3523

@hyorigo
Copy link
Author

hyorigo commented Aug 7, 2020

@alexec Thanks for your reply! So it's kinda design problem.

Is it hard/complicated to adjust Argo Workflow Controller for this purpose? Or it's nearly impossible to make such a change since it's the root of Argo and its design.

@CaramelMario
Copy link

The same. @alexec Is it a big big change, or maybe possible the fork and make a quick fix for this?

@stale
Copy link

stale bot commented Oct 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Oct 8, 2020
@stale stale bot closed this as completed Oct 15, 2020
@agilgur5 agilgur5 added area/multi-cluster type/support User support issue - likely not a bug labels Sep 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/multi-cluster type/support User support issue - likely not a bug
Projects
None yet
Development

No branches or pull requests

4 participants