CPUManager Support (allocate exclusive CPUs to containers) about k0s HOT 8 OPEN

I think leaving this open is fair, as this is a real blocker, i.e. there's no way to use CPUManager with k0s right now, unfortunately.

(And I consider this a bug, since nobody expected CPUManager not to work with k0s.)

To be clear, CPUManager can be used with k0s just not with reservedSystemCPUs. I installed k0s with arg --kubelet-extra-args='--cpu-manager-policy=static' and kubelet is running without error and I can see log entries for cpu_manager

from k0s.

This relates heavily on the same findings as in #4255 . Essentially we need to figure out better way to "default" cgroup settings without hardcoding anything like we do in some places currently

from k0s.

Thanks @jnummelin - Should I keep this issue open or close it in favor of #4255 and use that to track this feature also?

from k0s.

I think leaving this open is fair, as this is a real blocker, i.e. there's no way to use CPUManager with k0s right now, unfortunately.

(And I consider this a bug, since nobody expected CPUManager not to work with k0s.)

from k0s.

@twz123 - Noted, I will leave it open

from k0s.

Ah, good to know. Still, the hard coded cgroup related settings in k0s are something that needs to be addressed somehow.

from k0s.

In my case (k0sctl version: v0.17.5), --kubelet-extra-args='--cpu-manager-policy=static' was not enough, I had also set the resources reservation parameters:

installFlags:
- --debug
- --disable-components=konnectivity-server,metrics-server
- --kubelet-extra-args='--cpu-manager-policy=static --kube-reserved=cpu=500m,memory=1Gi --kube-reserved-cgroup=system.slice --kubelet-cgroups=/system.slice/containerd.service'

from k0s.

I had also set the resources reservation parameters:

Correct! I'm also specifying those (I should have mentioned that my previous comment).

from k0s.