Most Kubernetes workloads are services that run continuously and must be available at all times — the Deployment and StatefulSet controllers model these correctly. But two other workload patterns are equally important and modelled by different controllers: per-node workloads that must run exactly one instance on every node regardless of the node count, and batch workloads that run to completion rather than running indefinitely. DaemonSets ensure that exactly one Pod runs on every node (or every node matching a nodeSelector), automatically creating a Pod when a new node joins the cluster and deleting it when a node leaves. Jobs run one or more Pods to completion and track the number of successful completions, retrying failed Pods up to a configurable limit — making them the correct controller for database migrations, data pipeline runs, report generation, and any workload where success means finishing rather than running continuously.
25 minintermediate
DaemonSets and Jobs — node-level workloads and batch processing
Analogy🏏Cricket
🏏 Think of it like cricket: The Pod-ReplicaSet-Deployment hierarchy maps precisely onto the three levels of IPL franchise team management. A Pod is a single player on the field at a given moment — the smallest unit of participation, carrying its own identity and fulfilling a specific role in the current game. A ReplicaSet is the franchise's match-day playing XI contract — it specifies that exactly eleven players matching a specific profile must always be on the field; if one is injured and leaves, the team management immediately sends a substitute of the same profile to restore the count. A Deployment is the franchise's season-long team strategy — it manages how the playing XI evolves between matches: when a new batting approach is adopted, the Deployment replaces the old XI with the new one in a controlled rolling substitution rather than swapping all eleven players simultaneously and disrupting team cohesion. Just as the franchise director does not manage individual players directly — the playing XI contract (ReplicaSet) handles the count and the season strategy (Deployment) handles the transitions — you never manage Pods directly in production; the Deployment manages the transition and the ReplicaSet maintains the count. This reveals why the three-level hierarchy exists rather than one omnibus 'workload' object: each level solves one specific problem, and composing three focused abstractions produces better separation of concerns than one object that conflates scheduling, scaling, and update management.
Lesson 16 of 33
0% complete