Pod Volumes and Data Lifetime

In plain Docker, a container's own writable filesystem layer disappears the instant the container is removed - anything written there is gone. Kubernetes Pod volumes solve part of that problem: a volume attached to a Pod survives a container inside it crashing and restarting, because the volume is scoped to the Pod, not the individual container. But that is a narrower guarantee than it sounds, because it usually does not survive the Pod itself being replaced - and Pods get replaced far more often than beginners expect, including during ordinary node maintenance or a routine reschedule. Kubernetes offers several different volume types for different needs: emptyDir is simple scratch space that lives only as long as its Pod does, useful for temporary working files or a shared cache between two containers in the same Pod; configMap, secret and projected volumes are ways to inject configuration or credential data as files (as introduced in the previous module); and CSI (Container Storage Interface) volumes connect to real external, durable storage systems - these are what you actually want for data that must survive a Pod being deleted and recreated elsewhere. The core skill this module builds is matching a volume's actual lifetime and access guarantees to how important the data really is to lose.

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 database process writes all of its data into an emptyDir volume, and it passes every test the team throws at it - container crashes, container restarts, even a full Pod restart on the same node - because emptyDir genuinely does survive those. Then a routine node drain for maintenance reschedules the Pod onto a different node, and every byte of that data is gone permanently, because emptyDir never claimed to survive Pod-to-different-node rescheduling in the first place. The team's testing only ever exercised the boundary the volume type actually protects, and never tested the boundary that mattered for a database - which is exactly why matching volume type to data importance has to happen at design time, not discovered during an incident.

Name the durability boundary

The container writable layer follows one container. emptyDir follows one Pod and survives container restart, but disappears when that Pod is removed from its node. A PVC can follow replacement Pods subject to access mode, topology and driver behavior. Test both container restart and Pod reschedule because they cross different boundaries. Use kubectl describe pod to connect mount failures to claims and events.

Scenario: A cache in emptyDir is acceptable because it can be rebuilt; an upload queue in the same volume is not because node maintenance loses acknowledged work. Classify data by recovery requirement rather than convenience.
Warning: hostPath couples a workload to node layout and carries serious privilege risk. It is appropriate for tightly controlled node agents, not general application persistence.

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 pvc-storageclass-binding. Open /labs/kubernetes, choose pvc-storageclass-binding, 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.