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 API server static pod manifest:
-
On every control plane node, edit the manifest to ensure the
--profilingflag is set to false in the kube-apiserver command:If there is no existing--profilingflag, add- --profiling=falseunder thecommand:(orargs:) list forkube-apiserverusing a text editor such as:and add a line: -
Wait for the kubelet on each control plane node to detect the manifest change and restart the
kube-apiserverstatic pod (this happens automatically). You can monitor restart with: -
On every control plane node, verify that the running kube-apiserver process includes
--profiling=falseand does not include--profiling=true:
Using kubectl
Using kubectl
kubectl cannot modify the kube-apiserver static pod manifest or its process flags, so it cannot be used to set --profiling=false. To remediate this finding, you must edit /etc/kubernetes/manifests/kube-apiserver.yaml directly on every control plane node; see the Manual Steps section for the exact procedure.Automation
Automation

