[sig-scheduling] Code Freeze Exception request for KEP-5732

[Heba Elayoty]

Hi all,

Enhancement status: beta
SIG: sig-scheduling
k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/5732
PRs # :

• https://github.com/kubernetes/kubernetes/pull/139604
• https://github.com/kubernetes/kubernetes/pull/139472
• https://github.com/kubernetes/kubernetes/pull/139565
• https://github.com/kubernetes/kubernetes/pull/139859
• https://github.com/kubernetes/kubernetes/pull/140611
• https://github.com/kubernetes/kubernetes/pull/140295 

Additional time needed (in calendar days):  7

Reason this enhancement is critical for this milestone: All implementations are complete and passing tests and we just need more time for review cycles.

Risks from adding code late: (to k8s stability, testing, etc.): low. Need to run scheduler-perf tests but there is already an additional perf test within these PRs for beta graduation. 

Risks from cutting enhancement: TAS(Topology-aware Scheduling) feature will delay the target GA deadline by the end of this year.


Thanks,

Heba

[Kensei Nakada]

+1 from me

Kensei (sanposhiho)

2026年7月21日(火) 3:35 Heba Elayoty <hebae...@gmail.com>:

--
You received this message because you are subscribed to the Google Groups "sig-scheduling" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sig-schedulin...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-scheduling/CAKy20xaJm6dnoTRpeE%3DytQcL%3DPR29vNF41aByBVb9Z05ZgsSzA%40mail.gmail.com.

[Dominik Marcinski]

+1, review of TAS PRs got starved by the higher priority WAS, WAP and CPG PRs, we should have cycles to proceed with these ones.

To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/sig-scheduling/CAHoNQuLxFk26JXT4VGh%3Dbvvx%2Bpu2JQChFgOvs_30u5408SM1Hg%40mail.gmail.com.

[Dipesh Rawat]

Hi all,

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

Given the amount of work and review still outstanding, we believe it is better to defer this KEP to v1.38 rather than rush the remaining work after Code Freeze.

We understand that part of the implementation has already landed. Please take the appropriate action for those changes, either reverting them if needed or ensuring any user facing changes that have already landed are properly documented.

Thank you for your understanding and contributions.

Thanks,
Dipesh
v1.37 Release Lead

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