Which Kubernetes object is designed for stateful workloads requiring stable network identities and persistent storage for each pod?

• A. Deployment
• B. DaemonSet
• C. StatefulSet
• D. Job

Answer: (C)

Stateful workloads need predictable, enduring identities and dedicated storage for each instance. A StatefulSet is built for exactly that: every pod gets a stable, unique network identity and an ordinal index (like app-0, app-1, etc.) that survives rescheduling. This makes it possible for other components to reliably connect to the same pod address over time, which is crucial for databases, queues, and other stateful services.

In addition, StatefulSet provisions per-pod storage, so each instance has its own durable volume that remains attached to the same pod identity even if the pod moves to a different node. This pairing of stable network identity and per-pod storage is what enables stateful applications to recover cleanly and maintain data integrity.

Deployments are great for stateless, scalable workloads where pod identities can change and storage is typically shared or ephemeral. DaemonSets ensure one pod per node, but they don’t provide stable per-pod identities or per-pod durable storage in the way StatefulSet does. Jobs run tasks to completion and don’t support long-running stateful services with persistent storage tied to a fixed identity.

So, for stateful workloads needing stable network identities and persistent per-pod storage, StatefulSet is the appropriate Kubernetes object.