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, back up the existing static pod manifest for the API server:
- Edit the API server manifest to add or update the
--profilingargument:
command: or args: list for kube-apiserver, ensure there is an entry:--profiling=true to --profiling=false.-
Save the file and exit the editor. The kubelet will detect the manifest change and automatically restart the
kube-apiserverstatic pod on that control plane node. Expect a brief control-plane disruption during the restart. -
After 30–60 seconds, verify on that control plane node that the process is running with
--profiling=false:
-
In the command line output for
kube-apiserver, confirm that--profiling=falseis present and that there is no--profiling=trueflag. - Repeat steps 1–5 on every control plane node.
Using kubectl
Using kubectl
kubectl cannot change the
--profiling flag because it is set in the static pod manifest on each control plane node, specifically in /etc/kubernetes/manifests/kube-apiserver.yaml. To remediate this finding, follow the guidance in the Manual Steps section and edit the file directly on every control plane node.Automation
Automation

