Repository navigation
DRA: Partitionable Devices #4815
Description
Enhancement Description
-
One-line enhancement description (can be used as a release note):
Add support for partitionable devices to DRA. -
Kubernetes Enhancement Proposal:
-
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): - Code (
k/k) update PR(s): - Docs (
k/website) update PR(s):
- KEP (
-
Alpha (v1.35):
- KEP (
k/enhancements) update PR(s): [KEP-4815] Update KEP for 1.35 #5515 - Code (
k/k) update PR(s): - Docs (
k/website) update PR(s):
- KEP (
-
Beta (v1.36)
- KEP (
k/enhancements) update PR(s): - Code (
k/k) update PR(s): - Docs (
k/website) update(s):
- KEP (
Metadata
Metadata
Labels
Denotes that an issue has been opted in to a releaseCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Scheduling.Denotes an issue tracking an enhancement targeted for Stable/GA statusDenotes an enhancement issue is actively being tracked by the Release TeamCategorizes an issue or PR as relevant to WG Device Management.
Activity
kannon92 commentedon Aug 30, 2024
/sig node
haircommander commentedon Sep 17, 2024
/milestone v1.32
/label lead-opted-in
dipesh-rawat commentedon Sep 24, 2024
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
alphafor v1.32 (correct me, if otherwise)/stage alpha
Here's where this enhancement currently stands:
implementableforlatest-milestone: v1.32.For this KEP, we would need to update the following:
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 commentedon Oct 8, 2024
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!
198 remaining items
tico88612 commentedon Sep 16, 2026
Hello @klueska 👋, 1.38 Enhancements team here.
This is a reminder of the upcoming PRR freeze on Tuesday 22nd September 2026 (AoE) / Wednesday 23th September 2026 12:00 UTC.
This enhancement is targeting stage
betafor 1.38 (correct me, if otherwise)Here's where this enhancement currently stands:
stage,latest-milestone, andmilestonestruct filled out.For this KEP, we would just need to update the following:
latest-milestoneto `v1.38Note that the PR is not required to be approved or merged by the PRR freeze deadline. Having the PRR questionnaire filled out by the deadline will help ensure that the PRR team has enough time to review your KEP before enhancements freeze on Tuesday 29th September 2026 (AoE) / Wednesday 30th September 2026 12:00 UTC. For more information on the PRR process, see here.
The status of this enhancement is marked as
At risk for PRR freeze. Please keep the issue description up-to-date with appropriate stages as well.If you anticipate missing PRR freeze, you can file an exception request in advance. Thank you!
tico88612 commentedon Sep 21, 2026
#6381 target GA.
/stage stable
tico88612 commentedon Sep 21, 2026
Hello @klueska 👋, 1.38 Enhancements team here.
This is a reminder of the upcoming KEP Readiness (formerly named PRR freeze) on Tuesday 22nd September 2026 (AoE) / Wednesday 23th September 2026 12:00 UTC.
This enhancement is targeting stage
stablefor v1.38 (correct me, if otherwise)Here's where this enhancement currently stands:
stage,latest-milestone, andmilestonestruct filled out.This enhancement has met all the KEP Readiness (formerly named PRR freeze) requirements.
However, as we look ahead to enhancements freeze on Tuesday 29th September 2026 (AoE) / Wednesday 30th September 2026 12:00 UTC, this enhancement is currently
At risk for enhancements freeze.Here's what still needs to be addressed:
implementableforlatest-milestone: v1.38.For this KEP, we would just need to update the following:
The enhancements freeze deadline is one week after KEP Readiness (formerly named PRR freeze). If you anticipate missing it, please file an exception request in advance. Thank you!
/label tracked/yes
tico88612 commentedon Sep 27, 2026
Hello @klueska 👋, v1.38 Enhancements team here.
Just checking in as we approach enhancements freeze on Tuesday 29th September 2026 (AoE) / Wednesday 30th September 2026 12:00 UTC.
This enhancement is targeting stage
stablefor v1.38 (correct me, if otherwise)Here’s where this enhancement currently stands:
implementableforlatest-milestone: v1.38. KEPs targetingstablewill need to be marked asimplementedafter code PRs are merged.With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀
The status of this enhancement is marked as
Tracked for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!/label tracked/yes
Caesarsage commentedon Oct 4, 2026
Hello @klueska 👋 v1.38 Docs team here!
Does the enhancement work planned for v1.38 require any new docs, or modifications to existing docs?
If yes, please follow the steps in Open a placeholder PR to open a PR against the dev-1.38 branch in the kubernetes/website repo. It can be just a
placeholder for now, and must be created before Thursday 29 October 2026 (AoE) / Friday 30 October 2026, 12:00 UTC.
If this enhancement does not need docs, just reply here saying so and we'll mark it accordingly — an explicit "no docs needed" is as helpful to us as a PR.
Please also add the placeholder PR link to this issue's description once it exists, so it's picked up by tracking automatically.
For background: Documenting for a release.
Thank you!
troychiu commentedon Oct 12, 2026
Hi I have created kubernetes/website#58033. Thank you.
Urvashi0109 commentedon Oct 13, 2026
Hi @klueska 👋 -- this is Urvashi from the v1.38 Communications Team!
For the 1.38 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!
Please note that feature blogs are optional and not mandatory. However, they are a great way to communicate to users about features which fall into (but not limited to) the following categories:
To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Thursday 5th November 2026 12:00 UTC? For more information about writing a blog, please find the release communications guidelines 📚
For easier tracking, please let us know whether you'd like to opt in or opt out. If you're opting in, please include the skeleton blog PR in your reply.
Tip
Some timeline to keep in mind:
Note
In your placeholder PR, use
XXcharacters for the blogdatein 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.troychiu commentedon Oct 13, 2026
Hi @Urvashi0109, DRA/wg device management will have a combined feature blog and this feature will be included. Thank you.