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:
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.
--
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.