KEP-5007: DRA Device Binding Conditions GA in 1.37

[ttsuuubasa]

• One-line PR description: updating KEP docs for graduation to GA

• Issue link: DRA: Device Binding Conditions #5007

• Other comments:
  This PR promotes the DRA Device Binding Conditions feature to GA for Kubernetes v1.37, incorporating refinements based on real-world usage feedback.

  1. Stage Promotion to GA

  • Updated stage: beta → stage: stable in kep.yaml
  • Updated latest-milestone: "v1.36" → "v1.37"

  2. GA criteria updates

  • Refine GA graduation requirements to:
    • Require at least one example of real-world usage
    • Explicitly allow time for community feedback

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

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ttsuuubasa
Once this PR has been reviewed and has the lgtm label, please assign deads2k, macsko for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• keps/prod-readiness/OWNERS
• keps/sig-scheduling/OWNERS

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

[k8s-ci-robot]

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.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

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.

[ttsuuubasa]

@klueska
I’d like to discuss the real-world usage requirement for Binding Conditions.

Based on Patrick’s comment, CoHDI does not seem to be an appropriate example. In contrast, I believe the NVIDIA DRA driver, which has been contributed to kubernetes-sigs, is a better representation of real-world usage.

We already have a PR that applies Binding Conditions to the NVIDIA DRA driver. kubernetes-sigs/dra-driver-nvidia-gpu#855
As a next step, I’d like to ask for support with performance evaluation.

If the results show no performance concerns and no need for additional APIs, I propose that we move forward with merging the PR.