-
Notifications
You must be signed in to change notification settings - Fork 14.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
add a doc for QueueingHint #43813
add a doc for QueueingHint #43813
Conversation
/cc @alculquicondor |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
/sig scheduling |
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
@tengqm Thanks, fixed based on your reviews. |
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 for docs.
Ready for tech review (by / on behalf of SIG Scheduling)
@@ -222,6 +222,26 @@ This is an informational extension point. Post-bind plugins are called after a | |||
Pod is successfully bound. This is the end of a binding cycle, and can be used | |||
to clean up associated resources. | |||
|
|||
### EnqueueExtension |
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.
This should go after PreEnqueue.
I wonder if we should rename ## Extension points
to ## Interfaces
, so that it's not confused with https://kubernetes.io/docs/reference/scheduling/config/#extension-points, which actually form part of the API.
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.
Sounds good, I rename this along with some wording changes in the doc.
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
@alculquicondor Thanks, modified the PR based on your reviews. |
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
content/en/docs/concepts/scheduling-eviction/scheduling-framework.md
Outdated
Show resolved
Hide resolved
so that the scheduler will retry the scheduling of the Pod. | ||
|
||
{{< note >}} | ||
QueueingHint is a beta-level field and is enabled by default in 1.28. |
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.
QueueingHint is a beta-level field and is enabled by default in 1.28. | |
QueueingHint is a beta-level feature and is enabled by default in 1.28. |
(it's not an API field)
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.
This isn't quite right either. Try something like “Queuing hint evaluation during scheduling is a beta-level feature…”, or “the QueueingHint scheduler frobnication is a beta feature…” (change frobnication to a suitable term).
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 go with:
QueueingHint evaluation during scheduling is a beta-level feature ..
/lgtm |
LGTM label has been added. Git tree hash: 587e9b976d7b755c73489cbd120869c03674eeb7
|
Taking Tim's comment as approval for merge. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: divya-mohan0209 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 |
ref: https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4247-queueinghint
It's not a mistake that I try to push this to main branch, not to v1.29 branch.
This KEP is under a unique situation where we assume this feature has been existing as beta since v1.28.