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:
The certification blueprint and working fast in the terminal
Cluster architecture and the control plane components
Pods, containers and the pod lifecycle
Workload controllers and ReplicaSets
Deployments and rollout control
Services and cluster networking
Network policies and service discovery
ConfigMaps, Secrets and configuration delivery
Persistent volumes, claims and storage classes
Resource requests, limits and quality of service
Scheduling, taints and affinity
RBAC and service accounts
Troubleshooting with logs and events
Node conditions, the CNI and cluster networking faults
Cluster upgrades and version skew
Node maintenance, draining and cluster upkeep
State store backup and cluster recovery
Pod security, admission and hardening
Cluster monitoring, metrics and log collection
Bootstrapping a cluster with kubeadm
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
The exam is a timed hands-on session in a live cluster, and almost every task reduces to reading an object, changing it and verifying the result.
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 ReplicaSet keeps a declared number of identical pods running, and a Deployment manages a ReplicaSet for you, so you should not write one by hand.
A rolling update replaces pods gradually, controlled by how many extra pods are allowed and how many existing pods may be unavailable at once.
A ClusterIP service is a virtual address from the service range, load balanced to ready endpoints inside the cluster only.
Questions this pack covers
How should you allocate time across the exam domains?
Which output format flags make a listing answerable fast?
What does the Kubernetes control plane actually consist of?
Why must the API server be the single write entry point?
Why do containers in a pod share a network namespace?
What does a particular exit code tell you about a stop?
Why should you almost never write a ReplicaSet by hand?
What does a Deployment add on top of a ReplicaSet?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
