IntermediateCloudContainersDevSecOps

Kubernetes Security

4 / 5

Liz Rice and Michael Hausenblas's freely-available O'Reilly short on the Kubernetes-specific security model: API server, RBAC, network policy, secrets, and the typical hardening steps that move a cluster from default to defensible.

Buy on Amazon

As an Amazon Associate we earn from qualifying purchases. The link above is sponsored.

Published
2018
Publisher
O'Reilly Media
Pages
99
Language
English

Read this if

Engineers spinning up their first production cluster who need the 99-page distillation of what to do before the first incident. The freely available PDF makes it the obvious 'send to the team' reference for Kubernetes hardening basics.

Skip this if

Readers needing depth on runtime detection, supply-chain integrity, multi-cluster identity, or service-mesh security; the book is deliberately a primer, not a comprehensive reference. By 2026 Pod Security Admission, Gateway API, and signed-image standards have moved past the book's coverage.

Key takeaways

  • The Kubernetes security model is API-server-centric — most attacks are RBAC and network-policy failures, and the book makes this its spine.
  • Default-deny network policy is the highest-leverage hardening step in any cluster, and the book's framing of why is the most quotable in print.
  • Treat it as the on-ramp — once you have the basics, graduate to Kubernetes Security and Observability (Creane / Gupta) and current CNCF guidance.

Notes

Available free from O'Reilly's site as the typical 'short' format. Pair with Container Security (Rice) for the layer below and with the Kubernetes documentation's own 'Securing a Cluster' guide as the live update. Dated only in that the field has moved; the conceptual scaffolding is still correct.