StopContainer currently releases claim CPU allocations before UnprepareResourceClaims runs.
The code comments already document this as a workaround and note that it assumes ResourceClaims are not shared across pods/containers. That is fine for current behavior because claim sharing is explicitly unsupported.
This issue is to track the assumption before future work changes the lifecycle model.
Related:
Suggested:
- document the current DRA/CDI/NRI lifetime invariant
- add tests around
StopContainer, UnprepareResourceClaims, and restart Synchronize
- revisit this before enabling claim sharing, preemption, or mixed allocation behavior
StopContainercurrently releases claim CPU allocations beforeUnprepareResourceClaimsruns.The code comments already document this as a workaround and note that it assumes ResourceClaims are not shared across pods/containers. That is fine for current behavior because claim sharing is explicitly unsupported.
This issue is to track the assumption before future work changes the lifecycle model.
Related:
Suggested:
StopContainer,UnprepareResourceClaims, and restartSynchronize