KEP-5945: DRA Optional Node Preparation#6104
Conversation
|
Skipping CI for Draft Pull Request. |
c1accea to
460d02e
Compare
460d02e to
e9d141d
Compare
|
|
||
| ## Summary | ||
|
|
||
| This KEP introduces **Optional Node Preparation** to Dynamic Resource Allocation (DRA), allowing a `DeviceClass` to declare that node preparation is not required. Currently, the kubelet assumes it must always coordinate with a node-local DRA driver via gRPC to prepare allocated devices before container start (`NodePrepareResources`), and to unprepare them during pod termination (`NodeUnprepareResources`). |
There was a problem hiding this comment.
Why DeviceClass? I think it probably should be the Device (ie, the ResourceSlice). The driver author should know if it needs preparation. DeviceClass is for the cluster administrator, who could easily make a mistake with this being at that level.
There was a problem hiding this comment.
Yeah what you mentioned makes sense to me. I updated the KEP to introduce fields in ResourceSlice. Placing them on Device seems repetitive and might inflate the size of ResourceSlice instance. We can always add them to Device if there are use cases.
2a44fde to
d091764
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: troychiu The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/wg device-management |
johnbelamaric
left a comment
There was a problem hiding this comment.
LGTM from the DRA perspective, have not reviewed the PRR section yet
Uh oh!
There was an error while loading. Please reload this page.