Exception Request for KEP-4680 Implementation

39 views
Skip to first unread message

Harshal Patil

unread,
Nov 6, 2025, 3:10:13 PM (4 days ago) Nov 6
to sig-...@kubernetes.io, releas...@kubernetes.io, kubernetes-...@googlegroups.com
Additional time needed (in calendar days, due end of day AoE):
  • 3 business days, until Tuesday
Reason this enhancement is critical for this milestone:
  • Device Health Status provides critical information about device used by the pod in case the device has failed or unhealthy, 
Risks from adding code late:
  • Low risk. The changes are guarded behind a feature gate AllocatedResourcesStatus. Existing and new e2e tests would ensure the changes associated with this PR don't break 
Risks from cutting enhancement:
  • Risk of having insufficient but critical device failure reporting in DRA.  

Mrunal

unread,
Nov 6, 2025, 3:13:53 PM (4 days ago) Nov 6
to Harshal Patil, sig-...@kubernetes.io, releas...@kubernetes.io, kubernetes-...@googlegroups.com
+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/CAHY10_%3DZwhb_nm%2BvwspoGturg92uZhYJmr3DsZ8e7b4fnEzoNQ%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages