-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
KEP-4247: Update criteria targeting to enable the QueueingHints by default #4877
Conversation
macsko
commented
Sep 26, 2024
- One-line PR description: Update the metrics and beta criteria as we are targeting to enable the feature by default in v1.32.
- Issue link: Per-plugin callback functions for accurate requeueing in kube-scheduler #4247
- Other comments:
Do we want to define more SLOs, e.g. for hints or event handling performance? If yes, I think we will need to come back to them later, when we get some numbers from scheduler_perf test cases that will be added. Right now, we have only SLOs related directly to scheduling process: enhancements/keps/sig-scheduling/4247-queueinghint/README.md Lines 856 to 860 in 4b9728d
|
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.
Can you make sure we are not missing any questions for the Production Readiness Questionnaire from the latest https://github.com/kubernetes/enhancements/blob/master/keps/NNNN-kep-template/README.md?
- No performance degradation is confirmed via scheduler_perf. | ||
- scheduler_perf covers the performance of most QueueingHintFn for in-tree plugins. | ||
- scheduler_perf runs with QueueingHint both enabled and disabled for all test cases. | ||
- Event handling duration is monitored using scheduler_perf. | ||
- The feature gate is enabled by default. | ||
- No bug report for a while after enabling it by default. | ||
|
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.
Have we mentioned any additional criteria that we might consider when going GA?
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.
I don't remember any that is not covered in Beta part.
After addressing all the issues, please assign to @wojtek-t for PRR. |
4b9728d
to
54f2f14
Compare
54f2f14
to
4cf5175
Compare
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, macsko 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 |
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, thanks @macsko!