KEP-5007: DRA Device Binding Conditions beta in 1.36 by ttsuuubasa · Pull Request #5846 · kubernetes/enhancements

ttsuuubasa · 2026-01-28T05:39:24Z

One-line PR description: updating KEP docs for promotion to beta

Issue link: DRA: Device Binding Conditions #5007

Other comments:
This PR promotes the DRA Device Binding Conditions feature from alpha to beta for Kubernetes v1.36, with enhancements based on DRA driver developer's feedback and metrics.

1. Stage Promotion to Beta
- Updated stage: alpha → stage: beta in kep.yaml
- Updated latest-milestone: "v1.35" → "v1.36"
2. Enhanced DRA Driver Developer's Feedback
- CoHDI: Added comprehensive feedback from CoHDI (Composable Hardware Device Infrastructure) testing, including scenarios for device pool changes and external controller bug identification
- NVIDIA DRA Driver: Added feedback from NVIDIA's k8s-dra-driver-gpu showcasing ComputeDomain support with Multi-Node NVLink and IMEX technology
3. Improved Monitoring & Observability
- New Metrics: Introduced two new metrics for better operational visibility:
  - scheduler_dra_bindingconditions_allocations_total:
    tracks scheduling attempts with success/failure/timeout status
  - scheduler_dra_bindingconditions_prebind_duration_seconds:
    measures PreBind phase duration with detailed labels
- Enhanced Detection: Replaced event log-based monitoring with metric-based detection for better automation
4. Clarified Feature Scope
- Added explicit non-goal: device pool migration as happy-path flow (deferred to separate KEP)
NOTE:
I addressed comments and suggestions from @johnbelamaric during the v1.35 review cycle:
KEP-5007: DRA Device Binding Conditions alpha in 1.35 #5487

/wg device-management
/sig scheduling
/cc @pohly @johnbelamaric @dom4ha

k8s-ci-robot · 2026-01-28T05:39:33Z

Hi @ttsuuubasa. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

kannon92

Please make sure to request a PRR review for the beta promotion.

kannon92 · 2026-01-29T01:50:23Z

/ok-to-test

ttsuuubasa · 2026-01-29T07:02:01Z

@kannon92
I received ack from @johnbelamaric to be the PRR review approver, and updated prod-readiness/sig-scheduling/5007.yaml accordingly.
Please let me know if this is the correct procedure.

dom4ha · 2026-02-02T09:47:43Z

keps/sig-scheduling/5007-device-attach-before-pod-scheduled/README.md

-  - Pods which are not bound yet (in api-server) and not unschedulable (in api-server) are not visible by cluster autoscaler, so there is a risk that the node will be turned down
- Additional tests are in Testgrid and linked in KEP
- Scheduler supports timeout configuration via command-line argument
+    - In this use case, the attachment scenario for moving devices between different pools is achieved through re-scheduling triggered by BindingFailureConditions. However, there remains an issue that device migration needs to be implemented using BindingConditions as a happy‑path flow. This will be addressed in a separate KEP and will be considered out of scope for the beta-graduation criteria.


+1 for decoupling Binding Conditions from the attachment, but I'm a bit skeptical whether the problem can be fixed easily (see discussion in kubernetes/kubernetes#135473 (comment)), so the question is whether the happy-path is really good enough and proved working?

@wojtek-t @sanposhiho @macsko WDYT?

Personally, I consider having at least one user of the happy path at the prototype stage (= PR fully implemented and reviewed, but maybe not merged because of release timing) sufficient for beta. But we should have one.

With "happy path" I meant the one we have right now, i.e. without update the allocation.

The happy path is planned to be implemented in NVIDIA's ComputeDomain case.
My team members are currently working on the implementation. We plan to submit a pull request to NVIDIA's DRA GitHub within the next two or three days.

I am on vacation through the end of this week. If you have a PR ready this week I will make a point to review it on Monday, Tuesday, and Wednesday before the feature freeze. Please be ready to respond to review comments daily so we can get it in good shape by your EOD on Wednesday.

Thank you very much!
All members of my team (implementation team) will ensure they can address any review comments you provide promptly.

@klueska
We created the PR. Please review it.

Ack. Will start looking on Monday.

ttsuuubasa · 2026-02-03T05:50:12Z

@johnbelamaric
We have agreement from @pohly and @dom4ha that the happy path for binding conditions specifically in the device‑attachment scenario is out of scope for this KEP, and that the feature can still proceed to beta graduation.
Given that, I’d like to hear your opinion as well.

dom4ha

Looks good to me, waiting for @johnbelamaric before I give approve

dom4ha · 2026-02-09T19:47:54Z

keps/sig-scheduling/5007-device-attach-before-pod-scheduled/kep.yaml

  - "@macsko"
  - "@sanposhiho"
 approvers:
  - "@alculquicondor"


You can put me as approver.

@dom4ha
Thank you for the review.
I’ve added you as an approver and pushed the latest changes.

johnbelamaric

/lgtm

Also approved for PRR. I will add the Prow command after SIG approval.

- Updated the Production Readiness Review questionnaire and introduced metrics for troubleshooting and operations. - Addressed review comments from the v1.35 PR kubernetes#5487. - Added Graduation Criteria for beta. - Clarify that happy-path device migration is out of scope for beta criteria Signed-off-by: Tsubasa Watanabe <w.tsubasa@fujitsu.com>

johnbelamaric

/lgtm

Also approved for PRR. I will add the Prow command after SIG approval.

- Updated the Production Readiness Review questionnaire and introduced metrics for troubleshooting and operations. - Addressed review comments from the v1.35 PR kubernetes#5487. - Added Graduation Criteria for beta. - Clarify that happy-path device migration is out of scope for beta criteria Signed-off-by: Tsubasa Watanabe <w.tsubasa@fujitsu.com>

ttsuuubasa · 2026-02-10T04:34:43Z

@johnbelamaric
Thank you for the review.
I pushed an update to add the approver, so could you please run the LGTM command again?
Just to confirm, does “SIG approval” mean an LGTM from @dom4ha?

dom4ha · 2026-02-10T09:50:36Z

/approve

johnbelamaric · 2026-02-10T18:16:29Z

/approve
/lgtm

k8s-ci-robot · 2026-02-10T18:16:39Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dom4ha, johnbelamaric, ttsuuubasa

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~keps/prod-readiness/OWNERS~~ [johnbelamaric]
~~keps/sig-scheduling/OWNERS~~ [dom4ha,johnbelamaric]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

ttsuuubasa · 2026-02-13T07:42:35Z

@johnbelamaric @dom4ha
Thank you for the approval.

k8s-ci-robot requested review from dom4ha, johnbelamaric and pohly January 28, 2026 05:39

k8s-ci-robot added wg/device-management Categorizes an issue or PR as relevant to WG Device Management. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. labels Jan 28, 2026

github-project-automation bot added this to Dynamic Resource Allocation and SIG Scheduling Jan 28, 2026

github-project-automation bot moved this to 🆕 New in Dynamic Resource Allocation Jan 28, 2026

k8s-ci-robot added the kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory label Jan 28, 2026

k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jan 28, 2026

pohly moved this from 🆕 New to 👀 In review in Dynamic Resource Allocation Jan 28, 2026

kannon92 requested changes Jan 29, 2026

View reviewed changes

github-project-automation bot moved this to Needs Review in SIG Scheduling Jan 29, 2026

k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 29, 2026

ttsuuubasa force-pushed the dra-device-binding-conditions branch from cbc56b6 to 55e918d Compare January 29, 2026 06:54

dom4ha reviewed Feb 2, 2026

View reviewed changes

ttsuuubasa mentioned this pull request Feb 3, 2026

DRA: Device Binding Conditions #5007

Open

20 tasks

hase1128 mentioned this pull request Feb 4, 2026

Reimplement release of workload pods in ComputeDomain in terms of BindingConditions NVIDIA/k8s-dra-driver-gpu#653

Open

dom4ha reviewed Feb 9, 2026

View reviewed changes

johnbelamaric reviewed Feb 10, 2026

View reviewed changes

k8s-ci-robot assigned johnbelamaric Feb 10, 2026

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 10, 2026

johnbelamaric reviewed Feb 10, 2026

View reviewed changes

k8s-ci-robot assigned johnbelamaric Feb 10, 2026

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 10, 2026

ttsuuubasa force-pushed the dra-device-binding-conditions branch from 55e918d to a89021d Compare February 10, 2026 04:30

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 10, 2026

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 10, 2026

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2026

k8s-ci-robot merged commit 834293c into kubernetes:master Feb 10, 2026
4 checks passed

k8s-ci-robot added this to the v1.36 milestone Feb 10, 2026

github-project-automation bot moved this from Needs Review to Done in SIG Scheduling Feb 10, 2026

pohly moved this from 👀 In review to ✅ Done in Dynamic Resource Allocation Feb 16, 2026

Conversation

ttsuuubasa commented Jan 28, 2026

1. Stage Promotion to Beta

2. Enhanced DRA Driver Developer's Feedback

3. Improved Monitoring & Observability

4. Clarified Feature Scope

Uh oh!

k8s-ci-robot commented Jan 28, 2026

Uh oh!

kannon92 left a comment

Choose a reason for hiding this comment

Uh oh!

kannon92 commented Jan 29, 2026

Uh oh!

ttsuuubasa commented Jan 29, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ttsuuubasa commented Feb 3, 2026

Uh oh!

dom4ha left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

johnbelamaric left a comment

Choose a reason for hiding this comment

Uh oh!

johnbelamaric left a comment

Choose a reason for hiding this comment

Uh oh!

ttsuuubasa commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dom4ha commented Feb 10, 2026

Uh oh!

johnbelamaric commented Feb 10, 2026

Uh oh!

k8s-ci-robot commented Feb 10, 2026

Uh oh!

Uh oh!

ttsuuubasa commented Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

ttsuuubasa commented Feb 10, 2026 •

edited

Loading