Workload Resources: Deployments Quiz

Three workload controllers, three different assumptions about identity and ordering. Deployments treat pods as interchangeable. StatefulSets give them stable identities and ordered operations. DaemonSets put one pod on every node. Choosing wrongly is one of the more expensive Kubernetes mistakes.

What this quiz covers

• RollingUpdate — the default strategy, and how it differs from Recreate
• maxSurge and maxUnavailable — the two numbers that control rollout speed and availability, including what maxUnavailable: 0 implies
• minReadySeconds — treating a pod as ready before it really is
• ReplicaSets — the layer between a Deployment and its pods, and how rollbacks use it
• StatefulSets — stable network identity, headless services, and what deleting a pod does
• DaemonSets — scheduling onto new nodes as they join the cluster

Common mistakes

• Setting maxUnavailable: 0 without maxSurge, which stalls the rollout completely
• Expecting a deleted StatefulSet pod to be replaced with a new identity — it comes back with the same one
• Managing ReplicaSets directly instead of letting the Deployment own them

Twenty questions below, each with an explanation.

Time's up