More Info:
Disable profiling, if not needed.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every control plane node, open the kube-controller-manager static pod manifest for editing:
-
In the
spec.containers[0].command(orargs) list, add or modify the profiling flag so it is explicitly disabled. Ensure there is only one--profilingentry and it is set tofalse, for example:Remove or correct any existing--profiling=true. -
Save the file and exit the editor. Because this is a static pod manifest under
/etc/kubernetes/manifests, the kubelet on the control plane node will automatically restart thekube-controller-managerpod to apply the new setting. This causes a brief restart of the controller-manager component. -
Wait for the
kube-controller-managerpod to be recreated and running:or, from any machine withkubectlaccess: -
On every control plane node, verify that the controller-manager process is now running with
--profiling=false:Confirm the command-line includes--profiling=falseand does not contain--profiling=trueor an unqualified--profilingflag.
Using kubectl
Using kubectl
kubectl cannot change the --profiling flag because it is set in the static pod manifest on each control plane node. To remediate this finding, you must edit /etc/kubernetes/manifests/kube-apiserver.yaml directly on every control plane node as described in the Manual Steps section.Automation
Automation

