Reason this enhancement is critical for this milestone: This long-overdue enhancement for sig-autoscaling will allow the community to tune the threshold under which pod autoscaling ignores fluctuations of the metric used for autoscaling. This threshold is currently hard-coded to 10%, which is (much) too high for large deployments (where 10% maps to a large number of pods), and for users that need fast autoscaling reactions.
Risks from adding code late: (to k8s stability, testing, etc.) Since the updated logic is behind a feature gate, this should be little risk.
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.) Users handling large deployments or users that need fast reaction time will continue facing poor pod autoscaling performances.
nina polshakova
unread,
Mar 21, 2025, 3:16:36 PM3/21/25
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to kubernetes-sig-release
Hi all,
The release team is APPROVING this exception request based on the discussion in the Slack thread[0]. Your updated deadline to merge all PRs for your KEP is 8:00pm PDT on Tuesday, 24th March 2025.
If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.