2 — Disaster Recovery

Kubernetes

A book-shaped table of contents for Kubernetes: cloud-native foundations, the CKAD/CKA/CKS certification tracks, control-plane internals, platform tooling, multi-cluster architecture, and MAANG-level system design and interview prep — cross-linking the existing Prometheus, Observability, and Platform Engineering chapters instead of duplicating them.

3 — Backup & Restore

Backing up etcd snapshots without also capturing PV data and CRDs restores a control plane that boots but manages nothing.

5 — Cost Optimization

Most Kubernetes clusters waste money on the requested-vs-used gap, not on compute price: pods routinely request two to three times what they actually consume, so right-sizing requests beats chasing spot-instance discounts.

1 — High Availability

Running three or more control-plane replicas behind a load balancer only buys availability if etcd quorum, not just the API server, survives the loss of any single node.

8 — Kubernetes Failure Modes

The most dangerous Kubernetes failures are control-plane and etcd degradations, not pod crashes, because they fail silently — the API server keeps serving stale state while nothing can actually be scheduled or reconciled.