StatefulSet Pod Management Policies
What You'll Learn
You'll learn how Kubernetes offers two different pod management policies—OrderedReady and Parallel—that control how StatefulSet pods are created, updated, and deleted.
Why Management Policies Matter
By default, StatefulSets deploy pods one at a time in strict order (pod-0, then pod-1, then pod-2). But not every stateful application needs this careful sequencing. Management policies let you choose the right balance between safety and speed.
OrderedReady: The Default Policy
OrderedReady is the cautious, sequential approach:
- Pods are created in ascending order (0, 1, 2...)
- Each pod must be Running and Ready before the next one starts
- Updates and deletions happen in reverse order (highest index first)
- Guarantees predictable, stable deployment
Use OrderedReady when: Your application requires one instance to be fully operational before starting the next—like a database cluster where the primary must initialize before replicas can join.
Think of it as: Building a tower of blocks where each level must be solid before adding the next.
Parallel: The Fast-Track Policy
Parallel removes the ordering constraint:
- All pods launch simultaneously
- No waiting for Ready status between pods
- Faster scaling and updates
- Still maintains stable pod identities and storage
Use Parallel when: Your stateful pods are independent and can initialize concurrently—like multiple cache instances that don't need coordination.
Think of it as: Assembling multiple standalone sculptures at once instead of one careful tower.
Setting the Policy
You specify the policy in your StatefulSet manifest using the podManagementPolicy field (set to either OrderedReady or Parallel).
Key Takeaway: Choose OrderedReady for applications requiring sequential initialization, and Parallel for independent stateful pods that can start simultaneously—both preserve stable identities and persistent storage.