Stable Network and Storage Identity

A Deployment (from the earlier release-strategies module) treats every replica as identical and interchangeable - any Pod can be swapped for any other with no consequence. Some software genuinely cannot work that way: a database cluster's members each need to keep the same identity over time so other members, and clients, can reliably find and trust them - which is exactly the gap StatefulSet fills. Instead of random Pod names, a StatefulSet gives each replica a stable, predictable ordinal name (db-0, db-1, db-2, ...), stable DNS reachable through a headless Service (a Service with clusterIP: None, which returns individual Pod addresses instead of one shared virtual IP), and, via volumeClaimTemplates, its own dedicated PersistentVolumeClaim per ordinal. Crucially, when a StatefulSet Pod is replaced - whether from a crash or a reschedule - its replacement keeps the exact same ordinal name and reattaches the exact same PVC it had before, rather than getting a fresh identity and empty storage. This gives applications a stable foundation to map "member 1" to "member 1's own data," every time - but it is important to be clear about what Kubernetes is and is not doing here: it faithfully preserves identity and storage attachment, but it has no idea what a database replication protocol is and does nothing to configure or manage that itself.

Analogy: Kubernetes is a thermostat, not a remote control. You declare the temperature; independent controllers measure reality and keep acting. Debugging means finding which sensor, rule or actuator prevents convergence.

Read the object as evidence

kubectl get RESOURCE NAME -n NAMESPACE -o yaml
kubectl describe RESOURCE NAME -n NAMESPACE
kubectl get events -n NAMESPACE --sort-by=.metadata.creationTimestamp
kubectl explain RESOURCE.spec

Do not memorize these as a ritual. The first command exposes desired and observed state, the second connects conditions and events, the third supplies a timeline, and the fourth checks the server's schema. Compare what the controller was asked to do with what it reports doing. Then test the narrowest hypothesis.

Scenario: A Redis cluster's own internal logic tracks which member is which by hostname, expecting that identity to stay stable over the cluster's lifetime. If those Redis Pods were deployed as a plain Deployment instead of a StatefulSet, replacing a Pod would hand it a brand-new, randomly-generated name and a fresh, empty volume - completely confusing Redis's own membership bookkeeping and data-recovery logic, which was relying on that name staying put. A StatefulSet fixes exactly that mismatch by making Pod identity predictable and consistent across replacement - but it is still entirely on Redis's own replication protocol to correctly use that stable identity to actually recover and stay in sync.

Separate identity from replication

A StatefulSet produces stable ordinal names, ordered membership and, with volumeClaimTemplates, a claim per ordinal. A headless Service provides DNS such as db-0.db.ns.svc. These primitives let an application find members and reattach data; they do not elect leaders, copy data or fence split brains. Inspect Pod ordinal, PVC and application member ID together.

Scenario: db-1 is recreated with its original PVC but rejoins with stale data. Kubernetes preserved identity exactly; the database must perform log catch-up or restore before serving.
Warning: Deleting and recreating a StatefulSet with changed selectors or claim templates can break ownership assumptions. Plan migrations around stable names and retained claims.

Production reasoning

Ask four questions: Who owns this object? What dependency must become ready next? Which controller reports the blocking condition? What evidence would disprove my current theory? This prevents symptom-driven changes. Record the context, namespace, object generation, image digest and recent rollout before mutation; a recreated Pod may erase the evidence you needed.

Warning: Running is not the same as ready, healthy, durable or correct. Kubernetes status is layered. Confirm the application-level outcome as well as the object state.
Goal: Put this model into practice in the Kubernetes lab statefulset-redis-identity. Open /labs/kubernetes, choose statefulset-redis-identity, predict the failure path before changing anything, then use the simulator's check command to validate the finished state.

Deliberate practice

Before the lab, write the expected object relationship and the first three commands you will run. Afterward, explain why the fix converged and name one tempting change that would only mask the symptom. Repeat using an explicit namespace and a structured output format. This prediction-observation-explanation loop is what turns command familiarity into production judgment.

45-minute investigation

  1. Map (5 min): draw the owner-to-child chain and mark every namespace, selector, identity and dependency involved.
  2. Predict (5 min): write one expected status condition, one likely event and one log or metric signal before opening the lab.
  3. Observe (10 min): collect YAML, describe output and ordered events. Do not mutate state. Record which observation disproves your first theory.
  4. Repair (15 min): make the smallest declarative correction, watch the responsible controller converge, and verify the user-facing path rather than stopping at Running.
  5. Stress (10 min): change one relevant constraint - replica count, label, readiness, resource value or placement rule - predict the outcome, observe it, then restore the known-good declaration.
Tip: Keep a short incident note with symptom, evidence, hypothesis, change, result. Across four sections this produces a reusable runbook instead of a pile of remembered commands.