k8s-triage-robot
commented
4 weeks ago The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
PBundyra
What would you like to be added: A mechanism that would allow fallback to a different ResourceFlavor, if Kueue cannot start a job on assigned flavor.
Why is this needed: Currently, there is no fallback mechanism to a different flavor in Kueue. It means that if there is a free capacity in Kueue, but there are stockouts on the cloud provider side, Kueue will assign the same flavor over and over to a given Workload. This results in wasteful assignments VMs to a Workload that will not start (e.g. Workload will get repeatedly 5 VMs, when it needs 10 of them to start)
Users would like to be able to configure Kueue in a way, so that in case there are stockouts, Kueue will try a different flavor.
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.