DRA: Partitionable Devices

[klueska]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Add support for partitionable devices to DRA.

• Kubernetes Enhancement Proposal:

  • https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4815-dra-partitionable-devices
  • Incremental PRs:
    • KEP-4815: DRA Partitionable Devices #4874
    • KEP-4815 DRA Partitionable devices design update #5066
    • KEP-4815 DRA Partitionable devices support for multi-host #5069

• Discussion Link:

  • dra-evolution: partitioning of devices kubernetes-sigs/wg-device-management#20 (comment)
  • Paritionable model with grouped resources kubernetes-sigs/wg-device-management#29
  • Partitionable with common attributes kubernetes-sigs/wg-device-management#30
  • Partitionable model with a common shared shape kubernetes-sigs/wg-device-management#31
  • Partitionable model with generated partitions kubernetes-sigs/wg-device-management#32
  • WIP: Add a POC of an alternate partitioning scheme kubernetes-sigs/wg-device-management#35
  • Collecting different partitioning technologies / use cases here: https://docs.google.com/document/d/1lXGfnrBixRIMW9ESa-mv09Kisb2myVFV_A3nqPJ4FCQ/edit?tab=t.0#heading=h.rab8ucx2ufcl

• Primary contact (assignee):
  @klueska, @pohly, @johnbelamaric, @thockin, @cici37

• Responsible SIGs:
  /sig node

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

  • Alpha release target: 1.35
  • Beta release target: 1.36
  • Stable release target:

• Alpha

  • KEP (k/enhancements) update PR(s):
    • KEP-4815: DRA Partitionable Devices #4874
    • KEP-4815 DRA Partitionable devices design update #5066
    • KEP-4815 DRA Partitionable devices support for multi-host #5069
    • Update the API design for PartitionableDevice #5195
    • [KEP-4815] Update KEP for 1.35 #5515
  • Code (k/k) update PR(s):
    • [KEP-4815]DRA Partitionable device kubernetes#130764
  • Docs (k/website) update PR(s):
    • KEP-4815 DRA Partitionable Devices website#48530
    • Document DRA partitionable devices website#49868

• Alpha (v1.35):

  • KEP (k/enhancements) update PR(s): [KEP-4815] Update KEP for 1.35 #5515
  • Code (k/k) update PR(s):
    • Updates to DRA Partitionable Devices feature kubernetes#134189
  • Docs (k/website) update PR(s):

• Beta

  • KEP (k/enhancements) update PR(s):
    • KEP-4814: graduate DRA Partitionable Devices to beta #5767
  • Code (k/k) update PR(s):
    • Promote DRAPartitionableDevices to beta kubernetes#137350
    • Add partitionable devices upgrade/downgrade test. kubernetes#136655
  • Docs (k/website) update(s):
    • Docs update for KEP-4815 Partitionable Devices to beta website#54565

[kannon92]

/sig node

[haircommander]

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

[dipesh-rawat]

Hello @klueska 👋, v1.32 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 alpha for v1.32 (correct me, if otherwise)

/stage alpha

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.
• 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 need to update the following:

• Create the KEP readme using the latest template and merge it in the k/enhancements repo.
• Ensure that the KEP has undergone a production readiness review and has been merged into k/enhancements.

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. Thank you!

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