DRA: Extend PodResources to include resources from Dynamic Resource Allocation

[klueska]

Enhancement Description

• One-line enhancement description (can be used as a release note): An enhancement to the PodResources API to include resources allocated by drivers of Dynamic Resource Allocation (DRA).

• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3695-pod-resources-for-dra/README.md

• Discussion Link: https://github.com/kubernetes/kubernetes/pull/111023#pullrequestreview-1139709589 https://github.com/kubernetes/kubernetes/issues/113783 (As well as private slack messages)

• Primary contact (assignee): @klueska, @guptaNswati

• Responsible SIGs: /sig node

• Enhancement target (which target equals to which milestone):

  • Alpha release target: 1.27
  • Beta release target: 1.34
  • Stable release target: 1.36

• [x] Alpha

  • [X] KEP (k/enhancements) update PR(s):
    • https://github.com/kubernetes/enhancements/pull/3738
    • https://github.com/kubernetes/enhancements/pull/3915
    • https://github.com/kubernetes/enhancements/pull/4913
    • 1.32 https://github.com/kubernetes/enhancements/pull/4913/
  • [X] Code (k/k) update PR(s):
    • https://github.com/kubernetes/kubernetes/pull/115912
    • https://github.com/kubernetes/kubernetes/pull/115847
  • [x] Docs (k/website) update PR(s):
    • https://github.com/kubernetes/website/pull/39978

• [ ] Beta

  • [x] KEP (k/enhancements) update PR(s):
    • https://github.com/kubernetes/enhancements/pull/5346
  • [ ] Code (k/k) update PR(s):
    • TBD
  • [ ] Docs (k/website) update(s):
    • TBD

[klueska]

/milestone v1.27 /label lead-opted-in

[k8s-ci-robot]

@klueska: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.27 /label lead-opted-in

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/test-infra repository.

[k8s-ci-robot]

@klueska: Can not set label lead-opted-in: Must be member in one of these teams: [release-team-enhancements release-team-leads sig-api-machinery-leads sig-apps-leads sig-architecture-leads sig-auth-leads sig-autoscaling-leads sig-cli-leads sig-cloud-provider-leads sig-cluster-lifecycle-leads sig-contributor-experience-leads sig-docs-leads sig-instrumentation-leads sig-k8s-infra-leads sig-multicluster-leads sig-network-leads sig-node-leads sig-release-leads sig-scalability-leads sig-scheduling-leads sig-security-leads sig-storage-leads sig-testing-leads sig-windows-leads]

In response to this:

/milestone v1.27 /label lead-opted-in

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/test-infra repository.

[SergeyKanzhelev]

/milestone v1.27 /label lead-opted-in

[dchen1107]

/label lead-opted-in

I had trouble to add lead-opted-in last couple of days. Trying it one more time ...

[SergeyKanzhelev]

/stage alpha

[marosset]

Hello @klueska 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for v1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [ ] KEP readme using the latest template has been merged into the k/enhancements repo.
• [ ] KEP status is marked as implementable for latest-milestone: v1.27
• [ ] KEP readme has a updated detailed test plan section filled out
• [ ] KEP readme has up to date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

For this enhancement, it looks like https://github.com/kubernetes/enhancements/pull/3738 will address the remaining requirements.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[marosset]

This enhancement meets all of the requirements to be tracked in v1.27. Thanks!

[marosset]

Hi @klueska :wave:,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• [x] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [ ] All PRs are fully merged by the code freeze deadline.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:

• https://github.com/kubernetes/kubernetes/pull/115847

Please let me know if there are any other PRs in k/k I should be tracking for this KEP.

As always, we are here to help should questions come up. Thanks!

[klueska]

This is a dependent PR for the one you listed -- I have updated the description to include it: https://github.com/kubernetes/kubernetes/pull/115912

[Rishit-dagli]

Hi @klueska :wave:, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release. Please feel free to reach out with any questions. Thanks!

[klueska]

Docs placeholder added in description

[SergeyKanzhelev]

Based on SIG Node meeting on 05/02/2023 we do NOT plan this for 1.28 release. Please comment otherwise.

[klueska]

@moshe010 I don't think we can progress this to beta until DRA itself progresses to beta.

[moshe010]

@klueska I wasn't in the SIG Node meeting on 05/02/2023 which it was discussed and I never request this to be beta in 1.28. In the kep we stated that following: [1] alpha: "v1.27" beta: "v1.30" stable: "v1.32"

[1] - https://github.com/kubernetes/enhancements/pull/3915/files#diff-11e83115a85d63622d7dcdb3732b43f918caa972ff7f034a431f642227d22b2aL30-L32

[SergeyKanzhelev]

@klueska I wasn't in the SIG Node meeting on 05/02/2023 which it was discussed and I never request this to be beta in 1.28. In the kep we stated that following: [1] alpha: "v1.27" beta: "v1.30" stable: "v1.32"

[1] - https://github.com/kubernetes/enhancements/pull/3915/files#diff-11e83115a85d63622d7dcdb3732b43f918caa972ff7f034a431f642227d22b2aL30-L32

Updated this issue description

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

[pacoxu]

/sig network

As https://github.com/kubernetes/enhancements/pull/3915#issuecomment-1868322774, @aojea mentions that

we have this debate with accelerator network devices and several proposal on how to do it , it will not be nice if kubernetes ends with two different ways of configuring these devices

/remove-lifecycle stale

As this is still alpha, we should reach an agreement before promoting it to beta.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue 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 issues.

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle rotten

[SergeyKanzhelev]

/remove-lifecycle rotten

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

[klueska]

/remove-lifecycle stale

[haircommander]

/milestone v1.32 /label lead-opted-in

[aojea]

@haircommander this has to also go through SIG Network, it is clear stated in the KEP this is required for implementing networking functionalities, we have also a working group and a proposal https://github.com/kubernetes/enhancements/pull/4861 and we want to be sure both things are not conflicting and are aligned with the overall strategy

[haircommander]

@aojea would you like me to remove the milestone?

[aojea]

no, absolutely not, just allow us to participate in the review, so we can align work that happens in parallel

[haircommander]

absolutely! thanks for making explicit the dependency :)

[jenshu]

Hello @klueska 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage beta for v1.32 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [ ] KEP readme using the latest template has been merged into the k/enhancements repo.
• [ ] KEP status is marked as implementable for latest-milestone: v1.32.
• [x] KEP readme has up-to-date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

For this KEP, we would just need to update the following:

• [ ] In your kep README, it looks like content of the test plan is there, but can you please also insert the Test Plan header and checkbox, right above your unit tests section to match the template?
• [ ] In your kep.yaml you will need to set status: implementable and latest-milestone: "v1.32"
• [ ] In your PRR you will need to add a line targeting stage beta and an approver.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[ffromani]

Hello! I'm among the KEP wranglers that sig-node set up to help sig-node KEPs make progress smoothly during the 1.32 timeframe. Hello @moshe010 / @klueska / @adrianchiris, by reading the comments above it seems to me this KEP requires coordination with sig-network, is my understanding correct? In addition, does this KEP depend on other DRA features planned for the 1.32 cycle or is it independent wrt other DRA work? Thanks!