[Exception Request] KEP-5677: DRA Resource Pool Status — Code Freeze Exception for v1.36

[Noureldin]

Subject: Code Freeze Exception Request — DRA Resource Pool Status

---

Hi,

I am writing to request a code freeze exception for the following enhancement. Please find the details below:

• Enhancement name: DRA Resource Pool Status
• Enhancement status: Alpha
• SIG: SIG Node
• Enhancement issue: https://github.com/kubernetes/enhancements/issues/5677
• PR: https://github.com/kubernetes/kubernetes/pull/137028
• Additional time needed: 3 calendar days (due end of day AoE)

Reason this enhancement is critical for this milestone: This enhancement enables DRA drivers to expose pool-level status (device counts, availability) through a new API, addressing a key observability gap for DRA users. The implementation is complete and currently under review — only review feedback fixups remain.

Risks from adding code late: Low. The feature is entirely behind the DRAResourcePoolStatus alpha feature gate, which is off by default. It introduces a new API type (ResourcePoolStatusRequest) with its own dedicated controller, with no changes to existing code paths.

Risks from cutting the enhancement:  The feature addresses a key observability gap for DRA users — there is currently no way to query pool-level device status (counts, availability). Cutting would delay this capability to v1.37, extending the gap by another release cycle.

Please let me know if you need any additional information.

Thank you for your time and consideration.

[John Belamaric]

+1 this is really helpful for troubleshooting and understanding resource availability and has most of its approvals already 

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

[Noureldin]

Hi,

Following up on this request — we've received API approval from @liggitt on the PR: https://github.com/kubernetes/kubernetes/pull/137028#issuecomment-4090697608

The PR now has full approvals from liggitt, pohly, soltysh, and johnbelamaric. A /hold has been placed pending the exception approval in this thread, and we're ready to merge as soon as the hold is lifted.

Please let us know if anything else is needed from our side.

[Mrunal]

+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/d6bf4ea8-25f5-4d83-8a60-d8932a6e9cb2n%40googlegroups.com.

[Ryota]

Hi all,

The release team is APPROVING this exception request for KEP-5677 based on the discussion in the Slack thread[0].

Based on the 3 calendar day extension, your updated deadline to merge code + test PRs for this KEP is:
Saturday, 21st March, 2026 (Anywhere-on-Earth) / 12:00 UTC on Sunday, 22nd March, 2026

Thanks,
Ryota Sawada
v1.36 Release Team Lead

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