Case A05774 · Cloud · L3 Applied

Hardening a Kubernetes Cluster

Practise as: InterviewLevel: L3 Applied

Interview questionYou have just been handed a new managed Kubernetes cluster for production. What do you lock down first?

  1. 01 Answer
  2. 02 Example
  3. 03 Trade-offs
What a strong answer covers

Try it out loud first. Then check yourself:

  1. API server: private or IP-restricted endpoint, SSO-backed auth, audit logging on, no anonymous access
  2. RBAC: no day-to-day cluster-admin; treat create pods, exec and get secrets as privileged verbs
  3. Workloads: Pod Security Admission restricted, no privileged, hostPath or hostNetwork, non-root, enforced at admission
  4. Default-deny network policies, block pods from node metadata, and use workload identity instead of the node role
  5. Trade-off: restricted policies break legacy charts; roll out in warn and audit mode first, then enforce

If the interviewer pushes back

  • A pod can reach the node instance metadata endpoint. What does an attacker get, and how do you block it?

More Cloud cards

All Cloud cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09