CIS Benchmark: Harden the Kubelet and etcd
Fix all issues via configuration and restart the affected components to ensure the new settings take effect. Fix all of the following violations that were found against the kubelet: The cluster uses…
The task
Context
You must resolve issues that a CIS Benchmark tool found for the kubeadm provisioned cluster.
Task
Fix all issues via configuration and restart the affected components to ensure the new settings take effect.
Fix all of the following violations that were found against the kubelet:
The cluster uses the Docker Engine as its container runtime. If needed, use the docker command to troubleshoot running containers.
- Ensure that the
anonymous-authargument is set tofalse- FAIL - Ensure that the
--authorization-modeargument is not set toAlwaysAllow- FAIL
> Use Webhook authentication/authorization where possible.
Fix all of the following violations that were found against etcd:
- Ensure that the
--client-cert-authargument is set totrue- FAIL
*Lab note: this practice node runs containerd rather than the Docker Engine, so use crictl (or kubectl) where you would use docker.*
*Lab note: after restarting the kubelet the node may take up to 60 seconds to return to Ready.*
What this tests
Lock down network access, the kubelet, API authentication, and ingress TLS, and run CIS benchmark checks. On the CKS exam, Cluster Setup tasks are graded purely on what you build in the cluster - not multiple choice - so the only way to get faster is to do them on a real cluster against a clock.
Practice it for real
prepium.sh drops you into your own isolated Kubernetes cluster in the browser - no install, no credit card. You solve the task in a real terminal, hit validate, and a programmatic checker scores exactly what you got right and wrong (with partial credit). The canonical solution unlocks after you attempt it, so you learn the fast, exam-ready way to do it.