Request for code freeze exception for KEP-5237

18 views
Skip to first unread message

Michael McCune

unread,
Feb 9, 2026, 10:33:22 AM (10 days ago) Feb 9
to kubernetes-sig-cloud-provider, releas...@kubernetes.io, kubernetes-...@googlegroups.com
hello all,

I would like to request a code freeze exception for KEP-5237 so that we can get this KEP added to the milestone.

Enhancement name: CCM: watch-based route controller reconciliation using informers
Enhancement status (alpha/beta/stable): alpha
SIG: cloud-provider
k/enhancements repo issue #: 5237
PR #'s: 136539
Additional time needed (in calendar days, due end of day AoE): 0
Reason this enhancement is critical for this milestone: This change introduces a metric that is required for A/B testing the feature gate. Without it, promotion to beta would be delayed by at least one additional minor release.
Risks from adding code late: Cloud providers would be unable to properly A/B test and evaluate the feature gate behavior.
Risks from cutting enhancement: The implementation PR and the KEP update PR are already merged; only the KEP issue (5237) has not yet been added to the milestone.

peace o/

Josh Michielsen

unread,
Feb 10, 2026, 5:32:56 AM (9 days ago) Feb 10
to release-team, Michael McCune, kubernetes-sig-cloud-provider, kubernetes-...@googlegroups.com
I believe this was intended to be a PRR freeze exception request rather than a code freeze exception request. Context: https://github.com/kubernetes/enhancements/issues/5237#issuecomment-3866833544

Michael McCune

unread,
Feb 10, 2026, 8:37:34 AM (9 days ago) Feb 10
to Josh Michielsen, release-team, kubernetes-sig-cloud-provider, kubernetes-...@googlegroups.com
oh yes, my bad. this is indeed a PRR exception request.

peace o/
Reply all
Reply to author
Forward
0 new messages