[Do Not Merge] POC for Mixed CPU Allocation#149
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pravk03 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 |
4cdc990 to
944aa73
Compare
Remove flags that are on by default
This enables kube-scheduler and the Kubernetes control plane to track DRA claims directly against node allocatable CPU resources, this ensures 1. coordinated scheduling between DRA and non-DRA workload on the same node. 2. We no longer have to duplicate dra resources in the pod's standard request
944aa73 to
50df449
Compare
|
/cc I'm aware this it is a POC and about all the caveats, still very interested in this work! thanks for posting |
|
/cc |
|
/cc |
|
/cc |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
I will continue exploring this, but the progress is likely going to be slow as the v1.37 deadlines approach. Additionally, this work depends on KEP-5517 reaching Alpha 2 (hopefully in 1.37) so that Kubelet can set safe pod-level cgroup boundaries and container level limits to include DRA. |
POC for #103
This PR introduces Mixed Allocation Mode to the CPU DRA driver, enabling workloads to request both exclusive and shared CPUs.
Key Principles:
Flags:
--mixed-allocation-modeflag to enable or disable mixed allocation mode.--disable-node-allocatable-mappingflag to toggle native KEP-5517 scheduler accounting.DRA Hook:
NRI Hook: