KEP-5729: DRA: ResourceClaim Support for Workloads#5736
KEP-5729: DRA: ResourceClaim Support for Workloads#5736k8s-ci-robot merged 55 commits intokubernetes:masterfrom
Conversation
nojnhuh
commented
Dec 12, 2025
- One-line PR description: Add initial draft for KEP-5729: DRA: ResourceClaim Support for Workloads
- Issue link: DRA: ResourceClaim Support for Workloads #5729
- Other comments:
Add KEP-5729: DRA: ResourceClaim Support for Workloads
|
I'm ready for feedback on the Summary and Motivation sections. Mostly want to make sure this is appropriately scoped w.r.t. #5732. /cc @wojtek-t @erictune @44past4 @helayoty @johnbelamaric I'm still working on the meat of the proposal and hope to have a draft of that ready to share by the middle of next week before I go on vacation through the end of the year. |
Add API
|
I've added the first draft of the API. Still working through the rest of the KEP, but I think that section is ready to start getting some feedback. /label api-review |
Update non-goal to clarify that scheduling is out of scope
Add ResourceClaim lifecycle
|
/assign |
Clarify when a generated ResourceClaim's name is stored in the Pod status
wojtek-t
left a comment
There was a problem hiding this comment.
This overall looks fine to me (both from PRR persepctive as well as with my scheduling hat) modulo the minor comments I added.
I will wait with approving for the SIG approval though.
Removed shared ResourceClaim from example
Track PodGroups' resourceClaimNames in Pod status
Update API example for v1alpha2
|
This looks good to me. |
Add milestone to implementation history
Update release checklist
|
/approve It's great to see this KEP finally addressing our concerns with ReservedFor size limitations and enables topology scheduling (TAS KEP #5733) based on implicit (multi-node) or explicit topologies (network topology). |
|
/approve PRR |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dom4ha, nojnhuh, wojtek-t The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Pod spec.workloadRef -> spec.schedulingGroup
Add dom4ha to approvers
Recommend finalizer to protect PodGroup deletion
|
/lgtm |
|
looks like this merged before I got a chance to look at the API bits, but talking with @johnbelamaric, the API bits sound analogous to pod without much that's novel ... doing the API review at impl time sounds fine, I'm happy to pick that up when you get the impl PR open |
|
/area workload-aware |