Code Freeze Exception Request for KEP #4563

[Filip Křepinský]

Hello Release Team,

we would like to request an exception for the following enhancement.

Enhancement name: EvictionRequest API
Enhancement status: alpha
SIG: Node (WG Node Lifecycle)
k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/4563
PR #'s:  
- https://github.com/kubernetes/kubernetes/pull/137050
- https://github.com/kubernetes/kubernetes/pull/137133

- https://github.com/kubernetes/kubernetes/pull/137396

Additional time needed: 5 days, Monday July 27th (AoE)

Reason this enhancement is critical for this milestone: This feature has already been shared with the Node Lifecycle audience and a demo of the feature was presented at KubeCon. Multiple companies have already reimplemented this in their internal systems, which shows the scale of agitation for the feature. Overall, the Node Lifecycle WG has received positive feedback about the anticipation surrounding the adoption and use of this feature. Missing the release would set back adoption and prevent users from achieving their pod and node maintenance goals.

Risks from adding code late: The API changes have been approved and are in the merge queue. The implementation is done, but we need more time for the review. One PR is still missing tests. The new API group and the feature is disabled by default, which poses low risk.

Risks from cutting enhancement: There is a risk of ecosystem divergence due to multiple companies building out of tree standards of this. Delaying the k8s development increases the maintenance and migration burden for these users. This impedes the roadmap of the entire working group and many other KEPs that will begin building on EvictionRequest. It also limits integration with the existing and upcoming APIs (e.g. Workload Aware Scheduling).

Thank you,

Filip

[Dawn Chen]

+1 from SIG Node. 

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-release/CAEp5ocirjXrTnuBU_JuLE38eU2tqgzSazNiBQ33x7CscjL7WDg%40mail.gmail.com.

[Dipesh Rawat]

Hi all,

After reviewing the request and the discussion in the referenced Slack thread [0], the Release Team is APPROVING this exception request.

Based on the 5 calendar day extension, the updated deadline for this KEP is: Monday, 27th July 2026 (Anywhere on Earth) / Tuesday, 28th July 2026, 12:00 UTC.

Please note that all remaining reviews and pending work needs to be completed within this extension. Otherwise, this will need to be deferred to a future release.

If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.

Thanks,
Dipesh Rawat
v1.37 Release Lead

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