-
Notifications
You must be signed in to change notification settings - Fork 183
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
feat: Add support for minValues in requirement for scheduling, consolidation layer and corresponding API changes. #963
Conversation
…bility based on minValues in requirement.
Hi @nikmohan123. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Pull Request Test Coverage Report for Build 7995389241Details
💛 - Coveralls |
Consider using the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really, really nice work. These changes are absolutely non-trivial
/lgtm
/approve
/hold Wait for other PRs that are being staged to be approved |
… the NodePool requirement. (#1) * Initial commit for introducing the API changes and modified tests to incorporate the API changes. * Wire the minValues from NodePool spec requirement into scheduling requirement. * Add functional tests and add validations. * Add more documentation. * Take in latest changes from main. * Bump the version of CRD. * Add more documentation. * Add additional logic to fail close. * Add minValues to the error string of requirement. * Restrict the minValues to 50. * Add tests for consolidation related to minValues in requirement. * Addressed few comments. * Added topology test. * Addressed rest of the comments. * Addressed more comments. * Addressed few more comments. * Fix error message order.
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
Really really awesome work here! 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
/remove-hold Nice work! Ship it! |
Created an issue to fix the corner case of the topology spread not behaving as expected with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jonathan-innis, nikmohan123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
Add support for minValues in requirement for scheduling and consolidation layer. This allows users to enforce higher flexibility constraints on Karpenter so that Karpenter adheres to spot best practices. By enforcing minValues on Karpenter NodePools with node.kubernetes.io/instance-type or karpenter.k8s.aws/instance-family , customers can ensure that launches will have a better chance of providing a highly available instance type by giving PCO more options.
How was this change tested?
make presubmit
Will add functional tests once the API structure has been finalized as the minValues is extracted from the requirement of the API.
Also manually tested by injecting the
minValues
into requirement and tested the scheduling and consolidation path.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.