-
I am trying to set up CPU management policies on RKE-2 node (intel NUC quad core i7 8th gen), but changes are not visible after server restart. I want to change policy from "none" to "static" We might be missing something. Changes were made to /etc/rancher/rke2/config.yaml. cpu-manager: true
cpu-manager-policy: static
cpu-manager-policy-options: full-pcpus-only=true
cpu-manager-reconcile-period: 0s
kube-reserved: cpu=1
system-reserved: cpu=1 **_After the changes and rke2-server restart, we are checking the CPU state at /var/lib/kubelet/cpu_manager_state "policyName":"none","defaultCpuSet":"","checksum":1353318690}_** I assume policy name should be static here if changes were applied correctly. Could anyone please help how rke2 can apply these changes and how can we test it once done ? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Assuming those are all kubelet args, what you want would look something like this: kubelet-arg:
- "cpu-manager=true"
- "cpu-manager-policy=static"
- "cpu-manager-policy-options=full-pcpus-only=true"
- "cpu-manager-reconcile-period=0s"
- "kubelet-reserved=cpu=1"
- "system-reserved=cpu=1" If you want to pass arguments to a specific Kubernetes component, you need to put them in the arg list for that component, not just directly as rke2 config. |
Beta Was this translation helpful? Give feedback.
-
Thanks! It is working. |
Beta Was this translation helpful? Give feedback.
Assuming those are all kubelet args, what you want would look something like this:
If you want to pass arguments to a specific Kubernetes component, you need to put them in the arg list for that component, not just directly as rke2 config.