Re: [Exception Request] KEP-5007: DRA Device Binding Conditions - Code Freeze Excepiton for v1.36

[Patrick Ohly]

"'Tsubasa Watanabe (Fujitsu)' via kubernetes-sig-release"
<kubernetes-...@googlegroups.com> writes:

> Subject: Code Freeze Exception Request — DRA Device Binding Conditions
>
> ________________________________
>
> Hi
>
> I am writing to request a code freeze exception for the following enhancement. Please find the details below:
>
> *
> Enhancement name: DRA Device Binding Conditions
> *
> Enhancement status (alpha/beta/stable): alpha
> *
> SIG: sig-scheduling, wg-device-management
> *
> k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/5007
> *
> PR #’s: https://github.com/kubernetes/kubernetes/pull/137795

This got merged, so the exception is not needed after all.

--
Best Regards

Patrick Ohly
Cloud Software Architect

[Tsubasa Watanabe (Fujitsu)]

Subject: Code Freeze Exception Request — DRA Device Binding Conditions

---

Hi

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

• Enhancement name: DRA Device Binding Conditions
• Enhancement status (alpha/beta/stable): alpha
• SIG: sig-scheduling, wg-device-management

• k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/5007

• PR #’s: https://github.com/kubernetes/kubernetes/pull/137795

• Additional time needed (in calendar days, due end of day AoE): 3 days (due March 21, 2026 AoE)
• Reason this enhancement is critical for this milestone: 
  
  
  This enhancement is intended to graduate to beta in v1.36.
  Work is already underway to launch products that have integrated this feature.
  Releasing it in this milestone is important to ensure that users of those products can receive proper support from the vendor.
  The implementation itself is already complete, and the only remaining work is to address test updates.
  
  
• Risks from adding code late: (to k8s stability, testing, etc.)
  
  
  Unless a DRA driver vendor explicitly opts in to using this feature, users are not impacted and the existing allocation logic continues to be used unchanged.
  
  
• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)
  
  
  If this feature remains alpha, users of products that have already integrated it may not be able to receive proper vendor support.
  This would delay the supportability 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.

 

Best Regards,

Tsubasa Watanabe (ttsuuubasa)