Request for PRR freeze exception for KEP-5237

[Michael McCune]

hello all,

I would like to request a PRR freeze exception for KEP-5237 so that we can get it added to the milestone. as mentioned in the slack thread[0], i am reposting this request.

i apologize for the tardiness of this request and for placing extra load on the release team. i realize i missed the original deadline and also incorrectly labeled my previous email. i will endeavor to be more timely, and more accurate, in the future.

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): 6
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/

[0]: https://kubernetes.slack.com/archives/C2C40FMNF/p1770669763149579

[Ryota]

Hi all,

The release team is APPROVING this exception request for KEP-5237 based on the discussion in the Slack thread[0]. We see all the PRR requirements are met.

Please note that, as discussed in the Slack thread[0], we will need to remind you how another exception request would not be accepted in the v1.36 release for this KEP, given the belated exception request.

Thanks,
Ryota Sawada
v1.36 Release Team Lead

[0]: https://kubernetes.slack.com/archives/C2C40FMNF/p1770669763149579