Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
Cluster architecture and the control plane
Pods and the container contract
Deployments and ReplicaSets
StatefulSets, DaemonSets and Jobs
Services, DNS and endpoint resolution
Ingress and the API gateway layer
NetworkPolicies and zero trust
ConfigMaps, Secrets and configuration delivery
Persistent storage and volume claims
Resource requests, limits and quality of service
Scheduling, taints, affinity and topology
Autoscaling across pods and nodes
Health probes and lifecycle hooks
Rolling updates, canaries and rollbacks
RBAC and service account security
Pod security and the image supply chain
Observability: metrics, logs and events
Dockerfiles, layers, caching and multi-stage builds
Container networking, registries and runtimes
Terraform state, planning and modules
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
A cluster is worker nodes running a container runtime plus the kubelet, fronted by a control plane that is a set of controllers rather than one process.
A pod is a group of co-located containers that share a network namespace and optional storage, and it is the smallest schedulable unit.
A Deployment owns ReplicaSets; each change to the pod template produces a new ReplicaSet with its own revision.
A StatefulSet gives each replica a stable ordinal name and a stable identity that survives rescheduling, which is what a database member needs.
A ClusterIP Service gets a virtual IP that is not assigned to any interface, and kube-proxy programs the dataplane to route to it.
An Ingress object is pure configuration with no behaviour of its own until an ingress controller in the cluster acts on it.
Questions this pack covers
What does the Kubernetes control plane actually consist of?
Why must the API server be the single write entry point?
What is the smallest thing Kubernetes will actually schedule?
Why do containers in one pod share a network namespace?
How does a Deployment converge on the requested replica count?
What exactly does a ReplicaSet add on top of a Deployment?
Why does a StatefulSet guarantee pod identity and ordering?
What problem does a headless Service solve for a StatefulSet?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
