Databases and queues care which replica is which. A StatefulSet gives each Pod a fixed identity: names NAME-0, NAME-1 and so on, a DNS entry POD.SERVICE.NAMESPACE.svc.cluster.local through a headless Service (clusterIP: None) named in serviceName, and its own claim created from volumeClaimTemplates and named TEMPLATE-NAME-ORDINAL. When a Pod is replaced, it keeps its name and reattaches its own claim.
By default Pods start one at a time in order, each only after the previous is Running and Ready, and scale down from the highest ordinal. A broken Pod 0 therefore holds up the rest, and the fix belongs in the template. Scaling down leaves claims behind so the data comes back with the replica.
Only a few fields can change on an existing StatefulSet: replicas, the template, the update strategy and the claim retention policy. Others, such as podManagementPolicy or the claim templates, mean deleting and recreating it.
Ordered Pods, their claims, and one replica's stable name.