Why persistent storage matters in Kubernetes - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is persistent storage important in Kubernetes?

Imagine you run an app in Kubernetes that needs to save user data. What happens if the app's container restarts without persistent storage?

A The data is lost because container storage is temporary.

B The data is saved automatically by Kubernetes.

C The app will never restart if storage is missing.

D The data is saved in the container image.

💡 Hint

Think about what happens to files inside a container when it stops.

Containers have temporary storage that disappears on restart. Persistent storage keeps data safe beyond container life.

💻 Command Output

intermediate

What does this command show about persistent volumes?

Run kubectl get pv in a cluster with two persistent volumes. What output do you expect?

Kubernetes

kubectl get pv

A Shows no output if no pods use volumes.

B Shows all pods using persistent volumes.

C Lists all persistent volumes with their status and capacity.

D Displays storage classes only.

💡 Hint

Persistent Volumes are cluster resources independent of pods.

The kubectl get pv command lists all persistent volumes with details like capacity and status.

🔀 Workflow

advanced

Order the steps to create and use persistent storage in Kubernetes

Put these steps in the correct order to use persistent storage in a Kubernetes app.

A 3,2,1,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about how storage is first made available, then requested, then used.

You first create storage (PV), then claim it (PVC), then use it in a Pod, and finally check it works.

❓ Troubleshoot

advanced

Why does my Pod fail to mount the PersistentVolumeClaim?

You created a PVC and a Pod that uses it, but the Pod stays in Pending state. What is the most likely cause?

A No matching PersistentVolume is available for the PVC.

B The Pod spec is missing the container image name.

C The PVC is bound but the Pod has no volume mount.

D The Kubernetes API server is down.

💡 Hint

Check if the PVC can find a PV that matches its request.

If no PV matches the PVC's storage class, size, or access mode, the PVC stays unbound and Pod cannot mount it.

✅ Best Practice

expert

Which practice ensures data safety with persistent storage in Kubernetes?

To protect important data stored in Kubernetes persistent volumes, which practice is best?

A Store data only inside container writable layers.

B Regularly back up PersistentVolume data using external tools.

C Rely on Kubernetes to automatically replicate PV data across nodes.

D Delete and recreate PVs frequently to refresh storage.

💡 Hint

Think about how to keep data safe beyond Kubernetes itself.

Kubernetes does not automatically back up PV data. External backup tools ensure data safety in case of failure.

Practice

1. Why is persistent storage important in Kubernetes?

easy

A. It speeds up container startup time

B. It manages network traffic between pods

C. It automatically scales the number of pods

D. It keeps data safe even if containers stop or restart

Solution

1. Step 1: Understand container lifecycle

   Containers can stop or restart anytime, losing any data stored inside them.

2. Step 2: Role of persistent storage

   Persistent storage keeps data safe beyond container life, so data is not lost.

3. Final Answer:

   It keeps data safe even if containers stop or restart -> Option D

4. Quick Check:

   Persistent storage = data safety beyond containers [OK]

Hint: Persistent storage saves data beyond container life [OK]

Common Mistakes:

• Thinking persistent storage speeds up containers
• Confusing storage with network management
• Assuming storage auto-scales pods

2. Which of the following is the correct way to request persistent storage in Kubernetes?

easy

A. kubectl get storageclass

B. kubectl create pod --storage

C. kubectl apply -f persistentvolumeclaim.yaml

D. kubectl delete pvc

Solution

1. Step 1: Identify how to request storage

   PersistentVolumeClaim (PVC) is used to request storage in Kubernetes.

2. Step 2: Correct command to apply PVC

   Using kubectl apply -f persistentvolumeclaim.yaml applies the PVC configuration.

3. Final Answer:

   kubectl apply -f persistentvolumeclaim.yaml -> Option C

4. Quick Check:

   Request storage with PVC YAML and apply [OK]

Hint: Use kubectl apply with PVC YAML to request storage [OK]

Common Mistakes:

• Using pod creation command to request storage
• Confusing storageclass listing with requesting storage
• Deleting PVC instead of creating it

3. Given this PersistentVolumeClaim YAML snippet:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi

What does ReadWriteOnce mean?

medium

A. The volume can be mounted as read-write by only one pod at a time

B. The volume is automatically deleted when pod stops

C. The volume is read-only for all pods

D. The volume can be mounted as read-write by many pods simultaneously

Solution

1. Step 1: Understand accessModes in PVC

   AccessModes define how many pods can mount the volume and with what permissions.

2. Step 2: Meaning of ReadWriteOnce

   ReadWriteOnce means only one pod can mount the volume as read-write at a time.

3. Final Answer:

   The volume can be mounted as read-write by only one pod at a time -> Option A

4. Quick Check:

   ReadWriteOnce = single pod read-write mount [OK]

Hint: ReadWriteOnce means single pod read-write access [OK]

Common Mistakes:

• Thinking ReadWriteOnce allows multiple pods
• Confusing read-only with ReadWriteOnce
• Assuming volume auto-deletes with pod

4. You created a PersistentVolumeClaim but your pod fails to mount the volume with error "volume not found". What is the most likely cause?

medium

A. The PersistentVolumeClaim name does not match the volume name in the pod spec

B. The pod spec is missing the container image

C. The PersistentVolumeClaim requested storage size is too small

D. The pod is missing resource limits

Solution

1. Step 1: Check volume mount configuration

   The pod must reference the PVC by the exact name to mount the volume.

2. Step 2: Identify cause of "volume not found" error

   If names don't match, Kubernetes cannot find the volume to mount.

3. Final Answer:

   The PersistentVolumeClaim name does not match the volume name in the pod spec -> Option A

4. Quick Check:

   Volume mount fails if PVC name mismatches [OK]

Hint: Match PVC name exactly in pod volume spec [OK]

Common Mistakes:

• Ignoring volume name mismatch
• Blaming container image for volume errors
• Assuming storage size causes mount failure

5. You want two pods to share the same persistent storage volume with read-write access at the same time. Which access mode should you specify in your PersistentVolumeClaim?

hard

A. ReadWriteOnce

B. ReadWriteMany

C. ReadOnlyMany

D. WriteOnce

Solution

1. Step 1: Understand access modes for sharing

   ReadWriteMany allows multiple pods to mount the volume as read-write simultaneously.

2. Step 2: Choose correct access mode for sharing

   Since two pods need read-write access at the same time, ReadWriteMany is required.

3. Final Answer:

   ReadWriteMany -> Option B

4. Quick Check:

   Multiple pods read-write = ReadWriteMany [OK]

Hint: Use ReadWriteMany for shared read-write access [OK]

Common Mistakes:

• Using ReadWriteOnce which allows only one pod
• Confusing ReadOnlyMany with read-write access
• Selecting non-existent WriteOnce mode