This repository was archived by the owner on Jan 9, 2023. It is now read-only.

Description
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
We are currently running kube services on the node (kubelet, docker, containerd) in their own slice (/podruntime.slice) to separate them from other system services and workloads and apply resource reservation separately. By default, services are placed in system.slice and I propose that we switch back to that default (contrary to this design proposal which I believe is more general) and run kube services in there also.
This would allow us to make a single reservation on the node for system.slice and to ensure that the kube and system services are given priority over each others resource if there is contention. Since we are not enforcing limits on resource usage of either kube or system services separately or ortherwise, this configuration would be simpler and preferential.
Anything else of interest:
This is the approach taken on GKE, presumably for the above reasons