Deployment versus StatefulSet
WHAT IT TESTS: choosing the right workload controller. OUTLINE: Deployments suit interchangeable stateless replicas, StatefulSets give stable identities, ordered rollout, and per-Pod persistent storage for stateful systems.
WHAT IT TESTS: whether you can match workload type to controller. ANSWER OUTLINE: a Deployment manages fungible, stateless Pods with random names, rolling updates, and any-order scaling, ideal for web servers and APIs. A StatefulSet gives each Pod a stable, ordinal identity, stable network name, ordered and graceful deployment and scaling, and its own persistent volume that survives rescheduling, ideal for databases and clustered stateful systems.
Read the original → interview
- #kubernetes
- #deployment
- #statefulset
- #stateful
- #workloads
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.