Add most-allocated custom scheduler to improve node utilization by pa… - #9783
Add most-allocated custom scheduler to improve node utilization by pa…#9783reruno wants to merge 1 commit into
Conversation
…cking prow jobs onto fewer nodes.
|
Welcome @reruno! |
|
Hi @reruno. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: reruno The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/ok-to-test |
…cking prow jobs onto fewer nodes.
What this PR does / why we need it:
Add most-allocated custom scheduler to improve node utilization by packing prow jobs onto fewer nodes.
Special notes for your reviewer:
kubernetes-sigs/kueue#12739 (comment)
If you are promoting an image, please make sure you have done the following:
I have verified the digest with gcrane and added it as a comment to the PR or in the body.
I'm promoting a multi-arch image that matches all the supported platforms of Kubernetes.
I'm not promoting a tag that resolves to latest or moving tags as these are not supported
registry.k8s.io is an immutable registry and I'll need to cut a new release if the digest is wrong.