-
Notifications
You must be signed in to change notification settings - Fork 256
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
Support Cluster-Autoscaler's ProvisioningRequest via two-stage admission #1136
Comments
/assign |
@trasc Could you update the issue description? I don't have any context as to why this feature is necessary. |
Sorry about that @tenzen-y. Updated the description. There is a KEP coming. We are thinking of using the cmd/experimental folder to avoid tying this to the release of 0.5 |
/assign @mwielgus |
@alculquicondor Alright. Thank you for the updates :)
It makes sense. IIUC, ProvisioningRequest is not yet released. |
/reopen |
@trasc: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What would you like to be added:
Use two-stage admission to support Cluster-Autoscaler's ProvisioningRequest
Why is this needed:
The ProvisioningRequest API allows to request new nodes without creating Pods. Kueue can use it to provide high guarantees that the admitted workloads will fit in the cluster.
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
The text was updated successfully, but these errors were encountered: