Exception Request for KEP-4680 Implementation

34 views
Skip to first unread message

Harshal Patil

unread,
Nov 6, 2025, 3:10:10 PMNov 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 PMNov 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.

Drew Hagen

unread,
Nov 10, 2025, 4:18:19 PMNov 10
to kubernetes-sig-release
Hi all,

The release team is APPROVING this exception request based on the discussion in the Slack thread[0]. Your updated deadline to merge code+test PRs for this KEP is: end of Day AoE Tuesday Nov 11th / 12:00 UTC  Nov 12th.
If you need any clarification, please feel free to reach out to us in the #sig-release Slack channel.

Thanks,
Drew Hagen
v1.35 Release Team Lead

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

Drew Hagen

unread,
Nov 12, 2025, 1:04:40 PMNov 12
to kubernetes-sig-release
Hi all,

Unfortunately, the code+test PRs for this KEP didn't meet the Code Freeze Criteria within the updated deadline. Hence, the KEP is removed from the v1.35 milestone.

We appreciate your understanding as our Release Team manages a high volume of KEPs and exception requests, and we need to keep the process moving forward. If you have any questions, you can reach out in the #sig-release[0] channel on Slack and we'll be happy to help.

Thanks so much for your contributions!

Drew Hagen
v1.35 Release Team Lead

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

Reply all
Reply to author
Forward
0 new messages