-
Notifications
You must be signed in to change notification settings - Fork 1.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
Configurable tolerance for Horizontal Pod Autoscalers #4951
Comments
/sig autoscaling |
If we plan for this KEP to land in 1.33, there are a few more steps needed to be completed: https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#submitting-a-kep-for-production-readiness-approval |
/label lead-opted-in |
@gjtempleton: The provided milestone is not valid for this repository. Milestones in this repository: [ Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/milestone v1.33 |
Hey @jm-franc,
My main worry is the Production Readiness Review. I'm not too familiar with the process, and I think the deadline is soon. |
Thanks Adrian! I sent #5094 and |
Perfect, thanks! |
Hello @jm-franc 👋, v1.33 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025. This enhancement is targeting stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
Thank you @fykaa ! I've submitted the PRR questionnaire that marks this feature as 'implementable' for review (#5094) and I hope to have it approved before the deadline. Fingers crossed :) Thank you, |
Hi @jm-franc 👋, 1.33 Enhancements team here, Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025. The current status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
Hello @jm-franc 👋, 1.33 Enhancements team here. Now that PR #5094 has been merged, all the KEP requirements are in place and merged into k/enhancements. Before the enhancement freeze, it would be appreciated if following nit could be addressed:
Aside from the minor nit mentioned above, this enhancement is all good for the upcoming enhancements freeze. 🚀 The status of this enhancement is now marked as /label tracked/yes |
Done & thank you Dipesh! |
Hello @jm-franc 👋, v1.33 Docs Lead here. Does this enhancement work planned for v1.33 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Thank you Ryan, will do! There are indeed updates required to the documentation. |
Enhancement Description
k/enhancements
) update PR(s): KEP-4951: Configurable tolerance for HPA #4954 KEP-4951: Fill PRR questionnaire #5094k/k
) update PR(s):k/website
) update PR(s):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: