PRR freeze exception request for KEP 5593 - Configure the max crashloopbackoff delay

[Hank Freund]

Enhancement name: Configure the max CrashLoopBackOff delay
Enhancement status (alpha/beta/stable): alpha?
SIG: Node
k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/5593
PR #’s: https://github.com/kubernetes/enhancements/pull/5594
Additional time needed (in calendar days, due end of day AoE): 2

This proposal is a split of the existing KEP-4603 into two KEPs. KEP-4603 adds: 1. tuning the default crashloopbackoff delay, and 2. exposing a configurable max crashloopbackoff delay. Each of those enhancements is behind its own feature gate.
The new KEP-5593 rewrites KEP-4603 to only focus on item 1. It also migrates all the text about item 2 into the new proposal. Since everything is already at alpha, the desire is to graduate KEP-5593 to beta at the same time.
I'd like some extra time to make sure all stakeholders are on the same page and on board.

[Ryota]

Hi Hank,

Ryota from the v1.35 release team here! I can get the discussion thread open with relevant people. Could you also specify the following points based on the freeze exception template?

- Reason this enhancement is critical for this milestone:
- Risks from adding code late: (to k8s stability, testing, etc.)
- Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)

Thanks,

Ryota

[Jenny Shu]

Hi all,

Per the slack discussion[0], there is no need for a PRR exception since the required PR was opened and the Release Team marked the KEP as `Tracked for PRR freeze` before the deadline. Thanks!

-Jenny (on behalf of the 1.35 release team)

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