KEP-2625: cpumanager full-pcpus-inly becomes GA

Declare the `full-pcpus-only` option is now GA. There are no functional changes or user actions needed, so we just update the relevant versions. Signed-off-by: Francesco Romani <[email protected]>

Author: ffromani

content/en/docs/concepts/policy/node-resource-managers.md

@@ -200,8 +200,8 @@ listed in alphabetical order:
 : Spread CPUs across different NUMA domains, aiming for an even balance between the selected domains
 (available since Kubernetes v1.23)
 
-`full-pcpus-only` (beta, visible by default)
-: Always allocate full physical cores (available since Kubernetes v1.22)
+`full-pcpus-only` (GA, visible by default)
+: Always allocate full physical cores (available since Kubernetes v1.22, GA since Kubernetes v1.33)
 
 `strict-cpu-reservation` (beta, visible by default)
 : Prevent all the pods regardless of their Quality of Service class to run on reserved CPUs

content/en/docs/tasks/administer-cluster/cpu-management-policies.md

@@ -151,7 +151,7 @@ using the following feature gates:
 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` (beta, visible by default) (1.22 or higher)
+* `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)