More Info:
Verifies that the kube-apiserver pod manifest file is owned by root:root. Correct ownership ensures only privileged users can modify control plane configuration.Risk Level
MediumAddress
SecurityCompliance Standards
- CIS Kubernetes
Triage and Remediation
- Remediation
Remediation
Manual Steps
Manual Steps
-
On every control plane node, confirm the kube-apiserver manifest file exists and note its current ownership:
-
On every control plane node, change the file owner and group to root:root:
-
(Optional) Confirm file permissions are still appropriate (read-only change, no restart impact):
-
Verify the fix on every control plane node using the audit command:
The output must be:
Using kubectl
Using kubectl
kubectl cannot change file ownership on control plane nodes, so it cannot be used to remediate this finding on
/etc/kubernetes/manifests/kube-apiserver.yaml. To fix this, you must adjust file ownership directly on every control plane node; see the Manual Steps section for the exact commands.Automation
Automation
- Run on: every control plane node.
- Changing ownership of this manifest does not restart the kube-apiserver by itself; only content changes to files under
/etc/kubernetes/manifeststrigger static pod restarts.

