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:
  dynamic resource allocation kubernetes#111023 (review)
  dynamic resource allocation: add DRA-managed resources to the PodResources API kubernetes#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

• Alpha

  • KEP (k/enhancements) update PR(s):
    • KEP-3695: extend pod resource API to for DRA #3738
    • PodResources API for DRA: match API with actual implementation in 1.27 #3915
    • KEP-3695: Update podResourceV1 API #4913
    • 1.32 KEP-3695: Update podResourceV1 API #4913
  • Code (k/k) update PR(s):
    • kubelet DRA: Add checkpointing mechanism in the DRA Manager kubernetes#115912
    • Extend the PodResources API to include resources allocated by DRA kubernetes#115847
  • Docs (k/website) update PR(s):
    • Extend PodResources API for Dynamic Resource Allocation website#39978

• Beta 1.34

  • KEP (k/enhancements) update PR(s):
    • kep-3695-beta update #5346
    • KEP-3695: Add updates around e2e tests #5430
  • Code (k/k) update PR(s):
    • e2e: node: fix podresources API feature label kubernetes#132345
    • Add feature gate enable test for KubeletPodResourcesGet kubernetes#132827
    • KEP-3695: add kubeletPodResources feature gate to Beta kubernetes#132940
  • Docs (k/website) update(s):
    • KEP-3695: node: dra: podresources: Beta in 1.34 website#51476
    • Blog with DRA updates in 1.34 website#51488

[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 #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!