-
Notifications
You must be signed in to change notification settings - Fork 15.1k
KEP-5142: Add SchedulerPopFromBackoffQ feature gate docs #49840
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-5142: Add SchedulerPopFromBackoffQ feature gate docs #49840
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hello @macsko 👋! I'm reaching out from the Docs team. Just checking in as we approach Docs Freeze on 8th April, 2025 18:00 PDT. |
@dipesh-rawat @katcosgrove I need a review before the docs freeze |
--- | ||
|
||
Improves scheduling queue behavior by popping pods from the backoffQ when the activeQ is empty. | ||
This allows to process potentially schedulable pods ASAP, eliminating a penalty effect of the backoff queue. |
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.
Is the gate for all kube-components, or is it only relevant to the scheduler?
My guess is that this is only relevant to the scheduler.
If this option is only for the kube-scheduler, why do we make it a feature gate (for cross-cutting features involving more than one component)?
Can we simply use the kube-scheduler config file for this?
Feature gates are "heavy switchces".
With no explicit documentation on which gates involve which component, a cluster operator may have to restart all kubelets and even kube-proxy on all nodes.
/hold
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.
Yes, it's a feature gate only for the kube-scheduler. There are also other feature flags for another enhancements that similarly are designed only for a kube-scheduler. I'm not sure if moving from a feature gate to the config file is a good idea given that we are in the enhancements and code freezes.
How can an explicit documentation look like?
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.
/hold cancel
This issue has been sent to sig-architecture for guidance. I'm not anticipating a decision before the deadline this time, so I'm lifting the hold.
@macsko This PR also require a technical review. Thanks! |
/cc @dom4ha @sanposhiho |
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
from sig-scheduling.
I'm feeling like we should add a simple doc page to describe the queue's architecture.
LGTM label has been added. Git tree hash: 8168754dafa5c88094960b4613ed12d9e952105c
|
@tengqm Need a Docs approval. Thanks! |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sanposhiho, tengqm 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 SchedulerPopFromBackoffQ feature gate to docs.
Issue
kubernetes/enhancements/issues/5142