-
Notifications
You must be signed in to change notification settings - Fork 10
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
Question about Multi-Cluster Volcano #15
Comments
Yes, we'd like to start a new repo for multi-cluster; and we'd like to work with community for that. Meanwhile, the multi-cluster will still focus on batch related workloads. @stackedsax , let's start a design doc to discus the detial if you're also interesting that :) |
@stackedsax I re-opened volcano-sh/federation for us to improve Volcano for multi-cluster scenario :) |
Thanks for doing that, @k82cn. I'm also interested to see where the conversation with the CNCF Batch System Initiative (BSI) Working Group goes. |
Yes, CNCF BSI WG is a better place for this discussion :) |
From a recent discussion at the CNCF Research User Group, I was asked to follow up here with a question about multi-cluster plans for Volcano.
I know that we discussed with some Volcano folks about multi-cluster ideas a few years ago but I think Volcano has stayed focused on scheduling within a single cluster since then. A couple different groups (including us at G-Research) developed multi-cluster batch-scheduling systems because we had that specific need. I was curious whether the topic of scheduling across multiple k8s clusters has come back up in the Volcano universe and what the current thoughts are there.
Thanks!
The text was updated successfully, but these errors were encountered: