DevOps Practitioner · Module 2: Kubernetes networking and storage · Lab
Solve a Pending PVC and Prove Data Persistence
45 min hands-on · Core
A local KinD or k3d cluster with its default local StorageClass; a demo app that writes counter rows.
Local guide: run the steps below on your own machine in order, then check the validation list.
Objectives
- Diagnose a Pending claim from its events and fix the class reference
- Prove a written row survives pod deletion through the bound claim
- State the durability limit of local-path storage in the record
Step 1
Stage the Pending claim
Claim storage with a misspelled StorageClass name. Quote the claim events naming the missing provisioner, correct the single word, and show the claim bound.
Step 2
Write and reschedule
Mount the bound claim in the demo app, write a counter row, delete the pod, and read the row back from the replacement. Record the delete, the remount and the read-back.
Step 3
Write the honesty note
Add one paragraph to the record: what this proved (claim-bind-mount machinery, survival of pod death) and what it did not prove (replication, node-loss survival, production durability).
How to confirm it worked
- Pending event naming the provisioner gap quoted
- One-word fix shown with the claim bound
- Row written, pod deleted, same row read back
- Honesty paragraph present and accurate