Static CPU Manager Policy Options

`BestEffort` and `Burstable` pods run. Containers in `Guaranteed` pods with fractional CPU `requests` also run on CPUs in the shared pool. Only containers that are both part of a `Guaranteed` pod and have integer CPU `requests` are assigned exclusive CPUs. {{< note >}} The kubelet requires a CPU reservation greater than zero be made using either `--kube-reserved` and/or `--system-reserved` or `--reserved-cpus` when the static policy is enabled. This is because zero CPU reservation would allow the shared pool to become empty. {{< /note >}} ### Static policy options {#cpu-policy-static--options} You can toggle groups of options on and off based upon their maturity level using the following feature gates: * `CPUManagerPolicyBetaOptions` default enabled. Disable to hide beta-level options. * `CPUManagerPolicyAlphaOptions` default disabled. Enable to show alpha-level options. You will still have to enable each option using the `CPUManagerPolicyOptions` kubelet option. The following policy options exist for the static `CPUManager` policy: * `full-pcpus-only` (GA, visible by default) (1.33 or higher) * `distribute-cpus-across-numa` (beta, visible by default) (1.33 or higher) * `align-by-socket` (alpha, hidden by default) (1.25 or higher) * `distribute-cpus-across-cores` (alpha, hidden by default) (1.31 or higher) * `strict-cpu-reservation` (beta, visible by default) (1.32 or higher) * `prefer-align-cpus-by-uncorecache` (alpha, hidden by default) (1.32 or higher) The `full-pcpus-only` option can be enabled by adding `full-pcpus-only=true` to the CPUManager policy options. Likewise, the `distribute-cpus-across-numa` option can be enabled by adding `distribute-cpus-across-numa=true` to the CPUManager policy options. When both are set, they are "additive" in the sense that CPUs will be distributed across NUMA nodes in chunks of full-pcpus rather than individual cores. The `align-by-socket` policy option can be enabled by adding `align-by-socket=true` to the `CPUManager` policy options. It is also additive to the `full-pcpus-only` and `distribute-cpus-across-numa` policy options. The `distribute-cpus-across-cores` option can be enabled by adding `distribute-cpus-across-cores=true` to the `CPUManager` policy options. It cannot be used with `full-pcpus-only` or `distribute-cpus-across-numa` policy options together at this moment. The `strict-cpu-reservation` option can be enabled by adding `strict-cpu-reservation=true` to the CPUManager policy options followed by removing the `/var/lib/kubelet/cpu_manager_state` file and restart kubelet. The `prefer-align-cpus-by-uncorecache` option can be enabled by adding the `prefer-align-cpus-by-uncorecache` to the `CPUManager` policy options. If incompatible options are used, the kubelet will fail to start with the error explained in the logs. For mode detail about the behavior of the individual options you can configure, please refer to the [Node ResourceManagers](/docs/concepts/policy/node-resource-managers) documentation.

This section details the various options available for the `static` CPU Manager policy in Kubernetes. These options control CPU allocation behavior, such as `full-pcpus-only`, `distribute-cpus-across-numa`, `align-by-socket`, `distribute-cpus-across-cores`, `strict-cpu-reservation` and `prefer-align-cpus-by-uncorecache`. Each option can be enabled by adding it to the CPUManager policy options. Some options have specific compatibility requirements. It also refers to the Node ResourceManagers documentation for further information.