Secure the API Server (Anonymous Auth, Node,RBAC, NodeRestriction)
First, secure the cluster's API server configuring it as follows: Forbid anonymous authentication Use authorization mode Node,RBAC Use admission controller NodeRestriction The cluster uses the Docker…
The task
Context
For testing purposes, the kubeadm provisioned cluster's API server was configured to allow unauthenticated and unauthorized access.
Task
First, secure the cluster's API server configuring it as follows:
- Forbid anonymous authentication
- Use authorization mode
Node,RBAC - Use admission controller
NodeRestriction
The cluster uses the Docker Engine as its container runtime. If needed, use the docker command to troubleshoot running containers.
kubectl is configured to use unauthenticated and unauthorized access. You do not have to change it but be aware that kubectl will stop working once you have secured the cluster.
> You can use the cluster's original kubectl configuration file located at /etc/kubernetes/admin.conf to access the secured cluster.
Next, to clean up, remove the ClusterRoleBinding system:anonymous.
*Lab note: this practice node runs containerd rather than the Docker Engine, so use crictl (or kubectl) where you would use docker.*
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.