[v1.36 Exception Request] KEP-5759: Memory Manager Hugepages Availability Verification

2 views
Skip to first unread message

srikalyan swayampakula

unread,
Feb 17, 2026, 7:17:32 AM (2 days ago) Feb 17
to kubernete...@googlegroups.com, releas...@kubernetes.io, kubernetes-...@googlegroups.com
 Hi all,

  I'd like to request an enhancements freeze exception for KEP-5759.

  - Enhancement name: Memory Manager Hugepages Availability Verification
  - Enhancement status (alpha/beta/stable): alpha
  - SIG: sig-node
  - k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/5759
  - PR #'s: https://github.com/kubernetes/enhancements/pull/5753
  - Additional time needed (in calendar days, due end of day AoE): 3 days
  - Reason this enhancement is critical for this milestone: This KEP fixes a kubelet/workload contract
  breach where Guaranteed pods requesting hugepages are admitted by the Memory Manager but fail at runtime
   because Burstable pods have consumed the hugepages without being tracked. This is a known production
  issue (https://github.com/kubernetes/kubernetes/issues/134395). The KEP has received review from
  @johnbelamaric (PRR) and @ffromani (SIG Node), and all feedback has been addressed. We are awaiting
  final SIG Node /lgtm to merge.
  - Risks from adding code late (to k8s stability, testing, etc.): Minimal. This is an alpha feature
  behind the MemoryManagerHugepagesVerification feature gate, scoped to a single sysfs read during pod
  admission in the Memory Manager's Static policy. No API changes, no changes to default behavior.
  - Risks from cutting enhancement (partial implementation, critical customer usecase, etc.): Delays the
  fix for a known production issue affecting hugepage workloads. Users running mixed Guaranteed/Burstable
  hugepage workloads will continue to experience silent runtime failures.

  Thank you,
  -Srikalyan

Ryota

unread,
Feb 17, 2026, 7:36:10 PM (2 days ago) Feb 17
to release-team, srikalyan swayampakula, kubernete...@googlegroups.com, kubernetes-...@googlegroups.com
Hi all,

Unfortunately, the release team is REJECTING this exception request.

As mentioned in the Slack thread[0], exception requests must be submitted within three days after Enhancements Freeze per EXCEPTIONS.md[1]. We had a few other exception requests submitted in time and reviewed accordingly. We, the release team, are here to ensure smooth release management with reliability and fairness in mind, and thus cannot accept such delayed request.

We look forward to seeing this KEP to land as a part of the next v1.37 or future release, where it can receive proper review and tracking in time.

Thanks for your understanding and contributions!

Thanks,
Ryota Sawada
v1.36 Release Team Lead

[0]: https://kubernetes.slack.com/archives/C2C40FMNF/p1771312301013669
[1]: https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md
Reply all
Reply to author
Forward
0 new messages