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
A single scoring plugin for node resources #2458
Comments
/sig scheduling |
With PR #2461 merged, this enhancement meets all required criteria for the enhancements freeze 👍 |
Hi @ahg-g, Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:
As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them. Thanks! |
Hi @ahg-g, Enhancements team is marking this enhancement as "At Risk" for the upcoming code freeze due to not seeing any linked k/k PR(s) for this enhancement. Please make sure to provide all k/k PR(s) and k/website PR(s) to this issue so it can be tracked by the release team. |
Hi @ahg-g, A friendly reminder that Code freeze is 3 days away, March 9th EOD PST Any enhancements that are NOT code complete by the freeze will be removed from the milestone and will require an exception to be added back. Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST Thanks! |
/milestone v1.22 This enhancement will not make it. |
/milestone clear |
@JamesLaverack sorry, I missed to add this to the spreadsheet, I thought it was already there. The KEP is already merged and doesn't need updating. Can we add it back to v1.22? |
Hi @ahg-g, as per the discussion on the SIG Release mailing list, this enhancement's exception request has been approved. With #2741 merged your enhancement is in a good state for 1.22. I have added it to the tracking sheet. As a general comment, should the |
Hello @ahg-g 👋, 1.22 Docs Shadow here. 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. Thank you! 🙏 |
Hi @ahg-g, Also, the Doc Placeholder PR deadline is on July 9th, 2021. P.S. please let us know if there any k/k PRs need to be tracked for this one. Thank you! |
Thanks, implementation is merged. I will send the docs PR soon. |
@ahg-g Friendly reminder about the upcoming docs placeholder PR deadline on Fri July 9, 11:59 PM PDT. |
Updating the docs for this feature is dependent on updating the docs for scheduler's v1beta2 CC: kubernetes/kubernetes#95446 |
@ahg-g Today is docs placeholder deadline, please submit a placeholder PR by the end of the day, today! |
It is part of https://github.com/kubernetes/website/pull/28839/files |
all required PRs and docs merged. |
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 |
This will graduate with component config to GA. |
Enhancement Description
ScoreStrategy
).k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2458-node-resource-score-strategyk/k
) update PR(s): Add score func for NodeResourcesFit plugin Add score func for NodeResourcesFit plugin kubernetes#101822k/website
) update PR(s): https://github.com/kubernetes/website/pull/28839/filesPlease 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: