Claims request storage that a provisioner or existing volume can satisfy. Access modes, topology and reclaim behavior affect placement and data lifecycle.
Before you start
You should understand Pods, Deployments and Services. Read desired configuration separately from observed cluster state. Use a development cluster when trying changes, and inspect events and status rather than assuming that an accepted manifest means the workload is ready to serve traffic.
The practical goal is to reason through this situation: A Pod can remain pending because its claim cannot bind under available storage constraints. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.
Step-by-step walkthrough
Step 1: Trace claim binding
Check requested class, access modes, capacity and topology.
Step 2: Inspect placement constraints
A bound volume can still limit where a workload runs.
Step 3: Understand data lifecycle
Reclaim policy and backups determine what survives deletion and recovery.
Worked scenario
A Pod can remain pending because its claim cannot bind under available storage constraints.
A Pod remains pending because its claim cannot obtain suitable storage in the required topology. Recreating the Pod does not change the claim requirement. Deleting claims to force progress can affect stored data depending on policy, so diagnose binding evidence and preserve a recovery plan first.
Common mistake
Deleting a workload does not universally define what happens to stored data.
Verify the behavior
Inspect claim and provisioner events, then test restoration in an isolated environment.
Interview exercise
Protect persistent data.
Answer and reasoning
Understand reclaim policies, backups and restore procedures before deleting claims or migrating storage.
Continue learning
Compare the scenario with the Kubernetes interview questions and test your understanding with the Kubernetes MCQs. For terminology and implementation details, consult the reference material.