Exception Request for KEP-5007 Implementation

27 views
Skip to first unread message

Daisuke Kobayashi (Fujitsu)

unread,
Jul 24, 2025, 2:49:38 AMJul 24
to sig-sch...@kubernetes.io, wg-device-...@kubernetes.io, releas...@kubernetes.io, kubernetes-...@googlegroups.com, jbela...@google.com, patric...@intel.com
- Enhancement name:
- DRA: Device Binding Conditions

- Enhancement status (alpha/beta/stable):
- alpha

- SIG
- Scheduling

- k/enhancements repo issue #:
- https://github.com/kubernetes/enhancements/issues/5007
- PR #’s:
- https://github.com/kubernetes/kubernetes/pull/130160

- Additional time needed (in days):
- 6 (until Wednesday)

- Reason this enhancement is critical for this milestone:
- This enhancement is a key part of the broader Dynamic Resource Allocation (DRA) framework and is required to support advanced device scheduling use cases in future releases. Missing this enhancement would delay the adoption of DRA by vendors and users who rely on device-specific constraints.

- Risks from adding code late (to k8s stability, testing, etc.):
- This is a feature gated alpha feature with no default enablement. Therefore, risk is low adding this late. It has been under active review and testing, and no major regressions are expected.
- The risk is minimal as the code path is isolated and does not affect core scheduling logic unless explicitly enabled.

- Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)
- If this enhancement is cut, we lose the opportunity to gather early feedback from real-world use cases involving device binding. This would delay validation of the design and slow down iteration, affecting the roadmap for future DRA improvements.
- Several vendors and users are already preparing to adopt DRA in upcoming cycles, and missing this feature would hinder their ability to evaluate and integrate the framework effectively.


Thanks for your consideration.

Patrick Ohly

unread,
Jul 24, 2025, 5:03:33 AMJul 24
to Daisuke Kobayashi (Fujitsu), sig-sch...@kubernetes.io, wg-device-...@kubernetes.io, releas...@kubernetes.io, kubernetes-...@googlegroups.com, jbela...@google.com
"Daisuke Kobayashi (Fujitsu)" <kobayas...@fujitsu.com> writes:

> - Enhancement name:
> - DRA: Device Binding Conditions

+1 from me for DRA.

We had the DRA GA scheduled for 1.34 (almost done!) and four new
features (Consumable Capacity, Binding Conditions, Extended Resources,
Mixins). Sorting this all out despite vacations and public holidays simply
took a bit longer, but the last few weeks have been productive and it
feels that we are getting very close.

--
Best Regards

Patrick Ohly
Cloud Software Architect

Intel Deutschland GmbH
System Software Engineering/Cloud Native
Usenerstr. 5a Phone: +49-228-2493652
53129 Bonn
Germany

John Belamaric

unread,
Jul 24, 2025, 11:04:23 AMJul 24
to Patrick Ohly, Daisuke Kobayashi (Fujitsu), sig-sch...@kubernetes.io, wg-device-...@kubernetes.io, releas...@kubernetes.io, kubernetes-...@googlegroups.com
+1 from me too (DRA)

Dominik Marciński

unread,
Jul 24, 2025, 3:29:10 PMJul 24
to John Belamaric, Patrick Ohly, Daisuke Kobayashi (Fujitsu), sig-sch...@kubernetes.io, wg-device-...@kubernetes.io, releas...@kubernetes.io, kubernetes-...@googlegroups.com
+1 for sig-scheduling. I can add that the capacity of scheduling reviewers was very limited in this cycle due to my sick leave.

--
You received this message because you are subscribed to the Google Groups "wg-device-management" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wg-device-manage...@kubernetes.io.
To view this discussion visit https://groups.google.com/a/kubernetes.io/d/msgid/wg-device-management/CAC_Rkjwx4%2BTQaM%2BMJizWd26zVzcBaHhsJDDo%2B_mMTbTjxe1AHw%40mail.gmail.com.

Vyom Yadav

unread,
Jul 27, 2025, 4:15:37 PMJul 27
to release-team, Dominik Marciński, Patrick Ohly, Daisuke Kobayashi (Fujitsu), sig-sch...@kubernetes.io, wg-device-...@kubernetes.io, releas...@kubernetes.io, kubernetes-...@googlegroups.com, John Belamaric
The exception request has been APPROVED. The new deadline to get the relevant changes in is 02:00 UTC, 31st July. Slack Discussion: https://kubernetes.slack.com/archives/C2C40FMNF/p1753433771839429  
Reply all
Reply to author
Forward
0 new messages