[KEP-2941]: Supporting Dynamic Resource Allocations in Kueue

[kannon92]

What type of PR is this?

/kind feature

What this PR does / why we need it:

DRA support and Kueue

Which issue(s) this PR fixes:

KEP for #2941

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kannon92 Once this PR has been reviewed and has the lgtm label, please assign alculquicondor for approval. For more information see the Kubernetes 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:

• OWNERS

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

[netlify[bot]]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	a35c91120a359aaba478e20be415f25694c31e5a
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-kueue/deploys/66edb9d0d02bd6000814220b

[kannon92]

/cc @alculquicondor @mwielgus @tenzen-y @mimowo

[kannon92]

I brought this KEP up with wg-device-management. It seemed to over well and they pointed out a few improvements.

I added this KEP to the wg-batch agenda next week. Maybe from there we can continue to discuss this KEP.

[tenzen-y]

I brought this KEP up with wg-device-management. It seemed to over well and they pointed out a few improvements.

I added this KEP to the wg-batch agenda next week. Maybe from there we can continue to discuss this KEP.

Yeah, I'm open to discussion. But, I will start to review this PR after the 0.9 release due to the 0.9 release tight deadline.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[dweineha]

What's the status on this; has there been any progress? If not, is there anything I can do to help?

[kannon92]

What's the status on this; has there been any progress? If not, is there anything I can do to help?

AFAIK this was not a priority for 0.10 or 0.11 so it has not yet gotten reviews.

[kannon92]

@alaypatel07 is starting to looking into this.

[kannon92]

Thank you for the discussions. @alaypatel07 has opened up a new KEP.

thanks for continuing this useful Feature!

/close

[k8s-ci-robot]

@kannon92: Closed this PR.

In response to this:

Thank you for the discussions. @alaypatel07 has opened up a new KEP.

thanks for continuing this useful Feature!

/close

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.