Configurable tolerance for Horizontal Pod Autoscalers

[jm-franc]

Enhancement Description

• One-line enhancement description (can be used as a release note): Configurable tolerance for Horizontal Pod Autoscalers
• Kubernetes Enhancement Proposal: KEP-4951
• Discussion Link: Allow custom tolerance levels for horizontal pod autoscalers kubernetes#116984
• Primary contact (assignee): @jm-franc @pr00se
• Responsible SIGs: sig/autoscaling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4951: Configurable tolerance for HPA #4954 KEP-4951: Fill PRR questionnaire #5094
  • Code (k/k) update PR(s): Add support for HPA configurable tolerance kubernetes#130797
  • Docs (k/website) update PR: Add documentation for configurable autoscaling tolerance. website#49826 (Blog post PR)

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[jm-franc]

/sig autoscaling

[adrianmoisey]

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

[gjtempleton]

/label lead-opted-in
/milestone 1.33

[k8s-ci-robot]

@gjtempleton: The provided milestone is not valid for this repository. Milestones in this repository: [v1.25, v1.27, v1.28, v1.29, v1.30, v1.31, v1.32, v1.33, v1.34]

Use /milestone clear to clear the milestone.

In response to this:

/label lead-opted-in
/milestone 1.33

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.

[gjtempleton]

/milestone v1.33

[adrianmoisey]

Hey @jm-franc,
Your PR was approved and merged, and we have a lead-opted-in label here, so it seems like this KEP may be almost good to go with 1.33!
Just to help push it along, I think the following needs to happen:

• Ensure your enhancements meet the following requirements[2]
• Open an issue in kubernetes/enhancements[1] ✅
• Ensure that a kep.yaml exists with:
  • status[3] set to implementable ❌ (this needs to be done)
  • latest-milestone[4] set to the current release ✅
• A README.md exists that:
  • uses the latest template[5] ✅ (I think)
  • has the updated test plan[6] section filled out ✅ (I think)
• A Production Readiness Review[7] has been completed ❌ still to be done

My main worry is the Production Readiness Review. I'm not too familiar with the process, and I think the deadline is soon.
Let me know if there's anything I can do to help push this forward, it would be nice to see sig-autoscaling landing a KEP in 1.33!

[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. Let me know if there's anything I can do to help push this forward, it would be nice to see sig-autoscaling landing a KEP in 1.33!

Thanks Adrian! I sent #5094 and
#5093 for review, I hope they'll be merged before the Feb 6th deadline.

[adrianmoisey]

Perfect, thanks!

[fykaa]

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 alpha for v1.33 (correct me, if otherwise)
/stage alpha

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.33.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• KEP status should be marked as implementable
• KEP should have a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[jm-franc]

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 alpha for v1.33 (correct me, if otherwise) /stage alpha
[...]

• KEP should have a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

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,
JM

[dipesh-rawat]

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 At risk for enhancement freeze. There are a few requirements mentioned in the comment #4951 (comment) that still need to be completed.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[dipesh-rawat]

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:

• Update issue description to add the KEP update PR KEP-4951: Fill PRR questionnaire #5094 for alpha stage

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 tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!
(cc: @fykaa)

/label tracked/yes

[jm-franc]

• Update issue description to add the KEP update PR

Done & thank you Dipesh!

[rayandas]

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 dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[jm-franc]

Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?

Thank you Ryan, will do! There are indeed updates required to the documentation.

[jm-franc]

Hey @rayandas , I've created the website update draft PR as requested: kubernetes/website#49826

[aibarbetta]

Hi @jm-franc 👋 -- this is Agustina (@aibarbetta) from the 1.33 Communications Team!

For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[fykaa]

Hey again @jm-franc 👋, v1.33 Enhancements team here,

Just checking in as we approach Code Freeze at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• Add support for HPA configurable tolerance kubernetes#130797

Additionally, please let me know if there are any other PRs in k/k not listed above that we should track for this KEP, so that we can maintain accurate status.

If you anticipate missing code freeze, you can file an exception request in advance.

The status of this enhancement is marked as At risk for code freeze.

As always, we are here to help if any questions come up. Thanks!

[aibarbetta]

Hi @jm-franc 👋, 1.33 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 5th March, 2025. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 2025: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[jm-franc]

Hi @jm-franc 👋 -- this is Agustina (@aibarbetta) from the 1.33 Communications Team!

For the 1.33 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

Hey, thanks Agustina! I've opened kubernetes/website#50000

[jm-franc]

Hi & thanks @fykaa

If you anticipate missing code freeze, you can file an exception request in advance. Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

The status of this enhancement is marked as At risk for code freeze.

I've submitted the PR implementing this feature for review: kubernetes/kubernetes#130797

I hope this will be approved before the code freeze deadline, but please tell me if you think it would be prudent to file an exemption.

[dipesh-rawat]

Hi @jm-franc 👋, v1.33 Enhancements team here,

Just a quick friendly reminder as we approach the code freeze later this week, at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

The current status of this enhancement is marked as At risk for code freeze. There are a few requirements mentioned in the comment #4951 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

[jm-franc]

Hi @jm-franc 👋, v1.33 Enhancements team here,

Thanks Dipesh. The PR has been LGTMed by a SIG TL, and the SIG lead only had a few comments, so hopefully this will be ready to merge by the deadline tomorrow. My main concern is that we touch files that are not owned by sig-autoscaling; those changes are probably non-controversial but still I need to get manage to get approval.

[dipesh-rawat]

Hello @jm-franc 👋, v1.33 Enhancements team here,

Unfortunately, the implementation (code-related) PRs associated with this enhancement are not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.33 milestone.

An exception request has been received (https://groups.google.com/g/kubernetes-sig-release/c/wgcvmhAK75I) and is currently under evaluation. During this review period, the milestone has been removed. Depending on whether the request is approved or rejected, the milestone will be re-added accordingly. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/milestone clear

[dipesh-rawat]

Hello @jm-franc 👋, v1.33 Enhancements team here,

The release team has APPROVED the exception request here, so this KEP is now set to be added to the v1.33 release. The updated deadline to merge all related PRs is 8:00 PM PDT on Tuesday, March 25, 2025.

If you have any questions, feel free to reach out in the Exception Request thread on Slack in the #sig-release channel - we’re happy to help. Also, once the code PRs are merged, please feel free to let us know here. Thanks!

[dipesh-rawat]

@jm-franc With implementation PR kubernetes/kubernetes#130797 merged. This enhancement is now marked as tracked for code freeze for the v1.33 release!

/milestone v1.33

[raywainman]

/assign jm-franc