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
implement SchedulerQueueingHints feature gate #119328
implement SchedulerQueueingHints feature gate #119328
Conversation
/triage accepted |
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.
/approve
/lgtm
/assign @ahg-g
LGTM label has been added. Git tree hash: 90c8e7f74986e83b5e8e2b0f73a55da5234d2c91
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, alculquicondor, sanposhiho 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 |
Is there a docs proposal to k8s.io/website? The text in the commit message, especially the "user-facing" change is not easy to parse. |
It's more of a release note to developers of scheduler plugins. Maybe we should just remove the release note here, as the public for them is end users? |
OTOH, the feature gate is user facing. Let me try: /release-note-edit
|
@alculquicondor Thanks for handling 🙏 |
Changelog suggestion Added a new feature gate, `SchedulerQueueingHints` (enabled by default)
The new feature gate activates a framework for fine-grained filtering of events that related to
scheduler plugins.
In this release, no default scheduling plugins make use of the hinting framework, so you should not
expect any behavior changes. |
/release-note-edit
|
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Ref: #118438 (comment)
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: