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
Honor Nominated node during the new scheduling cycle #1923
Comments
/sig scheduling |
Hi @chendave Enhancements Lead here. Do you still plan to target this for alpha in 1.20? Thanks! |
@kikisdeliveryservice I have internal dependency on this, let me check the 1.20 release schedule first, and properly need to defer the milestone for this. |
Hi @chendave Any updates on whether this will be included in 1.20? Enhancements Freeze is October 6th and by that time we require: The KEP must be merged in an implementable state Thanks |
thank you @kikisdeliveryservice , I have updated the milestone to 1.21. |
Thank you for the update!! |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
/assign |
@kikisdeliveryservice I guess I need close this issue since the PR has been merged? see: kubernetes/kubernetes#93179 |
@kikisdeliveryservice @mvortizr let me close this issue, please feel free to reopen for some purpose like tracking. |
Hi @chendave , 1.21 Enhancements Lead here. The enhancements team is tracking this enhancement with the understanding that it has graduated to |
Hi @chendave ,
Thanks! |
@kendallroden @annajung thanks for the clarification. |
Hello @chendave , 1.21 Docs lead here. |
Hello @chendave 👋, 1.22 Docs release lead here. If it does, please follow the steps detailed in the documentation to open a PR against dev-1.22 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.
Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. |
Hi @PI-Victor , confirmed, no docs needed, thanks for the reminder! |
@chendave not quite, you'd need to at least update the default feature gate value to true. (tip: search |
Greetings @chendave ,
Thanks! |
@Huang-Wei I guess this should be auto-generated? just like this one: https://github.com/kubernetes/website/pull/25386/files Anyway, I will send one for review today. |
I see it, looks like I only need to update the feature gate, thanks for the guidance! @Huang-Wei |
@jrsapi still need another doc PR: kubernetes/website#28597. |
@jrsapi , the doc change has been covered by kubernetes/website#28644, no more changes is left for 1.22. |
@chendave Reminder that the code freeze is Thursday, July 7th and Docs Placeholder PR is Friday, July 8th. This is to notify that with the k/k PR's both merged, and a Docs PR is in place, this KEP is marked "Tracked" for the 1.22 milestone. Thanks! |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Can I close this one? since the feature is GA-ed. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
Enhancement Description
prefer nominated node - IMPL kubernetes#93179
Add KEP 1923 - prefer nominated node #2026
Graduate prefer nominated node to beta #2764
Graduate prefer nominated node to beta kubernetes#102201
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: