StatefulSet

A StatefulSet is a Kubernetes controller designed for stateful applications such as databases, message brokers, and distributed stores. Unlike a Deployment, it gives each pod a stable, persistent identity that survives rescheduling.

How It Works

Pods in a StatefulSet receive stable, ordinal names (for example db-0, db-1, db-2) and a stable network identity via a headless Service, so each pod is individually addressable. Each pod gets its own persistent volume through a volume claim template, and that storage stays bound to the same pod identity across restarts.

Operations are ordered and predictable: pods are created and scaled up sequentially from the lowest ordinal, and terminated in reverse order. Updates can roll out one pod at a time. This ordering matters for clustered software that requires a stable bootstrap sequence or a known primary.

Why It Matters

Many data systems assume stable hostnames, durable per-instance storage, and controlled startup order. A StatefulSet provides these guarantees natively, making it possible to run such systems on Kubernetes without losing data when pods move between nodes.

The trade-off is added complexity and slower scaling compared with stateless Deployments. StatefulSets do not eliminate the operational burden of running stateful systems; many teams pair them with an Operator that encodes backup, failover, and upgrade logic.

Related Terms

A StatefulSet manages pods with stable identity, binds each to a persistent volume, and uses a headless Service for addressing, in contrast to a stateless Deployment.