DRA: Add support for 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-node/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

• Responsible SIGs:
  /sig node

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

  • Alpha release target: 1.33
  • Beta release target: 1.34
  • Stable release target: 1.35

• 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
  • Code (k/k) update PR(s):
    • TBD
  • Docs (k/website) update PR(s):
    • KEP-4815 DRA Partitionable Devices website#48530

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

[dipesh-rawat]

Hi @klueska 👋, v1.32 Enhancements team here.

Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

The current status of this enhancement is marked as at risk for enhancement freeze. There are a few requirements mentioned in the comment #4815 (comment) that still need to be completed.

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

[dipesh-rawat]

@klueska Now that PR #4874 has been merged, all the KEP requirements are in place and merged into k/enhancements.

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

[chanieljdan]

Hi @klueska 👋, 1.32 Release Docs Lead here.

Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[chanieljdan]

Hi @klueska 👋, 1.32 Release Docs Lead here.

Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Hi @klueska 👋,

Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here). The deadline for this is a week away at Thursday October 24, 2024 18:00 PDT.

Thanks,

Daniel

[dipesh-rawat]

Hey again @klueska 👋 v1.32 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

I searched k/k and couldn’t find any recent PRs related to this KEP.

@klueska Please let me know the PRs in k/k that are not listed in the description or not linked with this GitHub issue that we need to track for this KEP, so that we can maintain accurate status.

The status of this enhancement is marked as at risk for code freeze.

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

[wrkode]

👋 Hi there, William here from v1.32 Comms
We'd love for you to consider writing a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[dipesh-rawat]

Hey again @klueska 👋, v1.32 Enhancements team here,

Just a quick friendly reminder as we approach code freeze in few days, at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

The current status of this enhancement is marked as at risk for code freeze. There are a few requirements mentioned in the comment #4815 (comment) that still need to be completed.

If you anticipate missing code freeze, you can file an exception request in advance.

[dipesh-rawat]

Hello @klueska 👋 v1.32 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.32 milestone.

If you still wish to progress this enhancement in v1.32, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/label tracked/no
/remove-label tracked/yes
/milestone clear

[Huang-Wei]

/label lead-opted-in

[bianbbc87]

Hello @klueska 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage alpha for v1.33 (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.33.
• 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 6th February 2025 so that the PRR team has enough time to review your KEP.

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

• 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 enhancements 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!

[bianbbc87]

Hi !
Please change the latest-milestone and alpha milestone of kep.yml to v1.33.

[johnbelamaric]

Hi ! Please change the latest-milestone and alpha milestone of kep.yml to v1.33.

See #5066 - I think that will merge soon.

[dipesh-rawat]

@klueska With PR #5066 covered most of the updates we need for inclusion of this KEP in v1.33.

Could I get a bit more clarification before we set the status of the KEP? In the issue description, I see another PR #5069 that modifies the KEP files and hasn’t been merged. Can one of the KEP contributors confirm if that PR isn’t part of the current release work and is something we’re doing incrementally for future? Maybe @johnbelamaric, you can help with this question. Apologies for the ping and any confusion!

[johnbelamaric]

Hi, yes, we do hope to add the work in #5069 in this release as well, but we would proceed with what we have if there is some issue with that. I expect (hope!) that will merge tomorrow when our European contributors have had a chance to review it.

[dipesh-rawat]

Hello @klueska @mortent 👋, 1.33 Enhancements team here.

Now that PRs #5069 #5066 has been merged, all the KEP requirements are in place and merged into k/enhancements.

Before the enhancement freeze, it would be appreciated if following nit could be addressed:

• Update issue description to add the correct link for KEP readme (the current link is broken).
  • Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/4815-dra-partitionable-devices/README.md

Aside from the minor nit mentioned above, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is now marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!
(cc: @bianbbc87)

/label tracked/yes

[rayandas]

Hello @klueska @mortent 👋, v1.33 Docs Lead here.

Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 2025 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[mortent]

Docs placeholder PR: kubernetes/website#49868

[rayandas]

Thanks @mortent Please add it in the issue description as well.