-
Notifications
You must be signed in to change notification settings - Fork 87
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
Cloud Burst Configuration -> Pod does not trigger auto-scale #202
Comments
Also I noticed, that even when my cloud cluster
on-prem cluster
Is this (another) bug? |
The virtual node should have capacity and allocatable including nvidia.com/gpu, as implemented here: https://github.com/admiraltyio/admiralty/tree/master/pkg/controllers/resources So I suspect a configuration issue. Are you able to run the quick start on these clusters? |
I have two clusters:
on-prem
: cluster with 2 GPU nodescloud
: cluster with 0-5 GPU nodes (auto-scaling is active)I tried to use the proposed solution for "cloud bursting":
on-prem
withmulticluster.admiralty.io/elect: ""
annotationon-prem
cluster as expectedPending
state forever, since admiralty doesn't even try to schedule on mycloud
cluster due to apparent missing resources (Insufficient nvidia.com/gpu
),How can I tell admiralty to schedule to my
cloud
cluster, even though currently there are no free resources available so the scheduled Pod can trigger auto-scaling?If this is not possible, I don't see the point of "Cloud Bursting" here since I'd need to have my cloud resources "always on" and pay for them.
The text was updated successfully, but these errors were encountered: