scheduler: KEP-5007 allocator test - devices w/wo BindingConditions

[ttsuuubasa]

What type of PR is this?

/kind feature
/sig scheduling

What this PR does / why we need it:

This PR adds a test case to verify allocation behavior when a single ResourceSlice contains both devices with and without BindingConditions.
It ensures that two requests within a single ResourceClaim can successfully allocate both types of devices.
This scenario reflects realistic usage patterns and helps validate that the scheduler correctly handles mixed device conditions, improving test coverage and robustness.

Which issue(s) this PR is related to:

Part of KEP-5007: DRA Device Binding Conditions

Special notes for your reviewer:

@johnbelamaric @dom4ha

This PR is one of the enhancements of test for Device Binding Conditions (KEP-5007) targeting v1.35, and it fulfills one of the graduation criteria described in the KEP (originally listed as a beta graduation criterion).

• Additional tests are in Testgrid and linked in KEP

To proactively meet the criteria for beta, we are considering merging this in the v1.35 alpha release.

@pohly

I’ve created one of the test cases you previously suggested in the comment.
Could you please take a look when you have a moment?

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/issues/5007

[k8s-ci-robot]

@ttsuuubasa: The label(s) kind/scheduler cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?

/kind feature
/kind scheduler

What this PR does / why we need it:

This PR adds a test case to verify allocation behavior when a single ResourceSlice contains both devices with and without BindingConditions.
It ensures that two requests within a single ResourceClaim can successfully allocate both types of devices.
This scenario reflects realistic usage patterns and helps validate that the scheduler correctly handles mixed device conditions, improving test coverage and robustness.

Which issue(s) this PR is related to:

Part of KEP-5007: DRA Device Binding Conditions

Special notes for your reviewer:

@johnbelamaric @dom4ha

This PR is one of the enhancements of test for Device Binding Conditions (KEP-5007) targeting v1.35, and it fulfills one of the graduation criteria described in the KEP (originally listed as a beta graduation criterion).

• Additional tests are in Testgrid and linked in KEP

To proactively meet the criteria for beta, we are considering merging this in the v1.35 alpha release.

@pohly

I’ve created one of the test cases you previously suggested in the comment.
Could you please take a look when you have a moment?

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: https://github.com/kubernetes/enhancements/issues/5007

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.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

Hi @ttsuuubasa. Thanks for your PR.

I'm waiting for a github.com 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.

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.

[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 pohly for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• staging/src/k8s.io/dynamic-resource-allocation/OWNERS

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

[ttsuuubasa]

/sig scheduling