Why persistent storage matters in Kubernetes - Quick Recap

Recall & Review

beginner

What is persistent storage in Kubernetes?

Persistent storage in Kubernetes is a way to save data beyond the life of a single container or pod, so data is not lost when pods restart or move.

beginner

Why do pods need persistent storage?

Pods need persistent storage to keep important data safe even if the pod crashes, restarts, or is deleted. Without it, data would be lost.

intermediate

What is a PersistentVolume (PV) in Kubernetes?

A PersistentVolume (PV) is a piece of storage in the cluster that has been provisioned by an administrator or dynamically created, ready to be used by pods.

intermediate

How does a PersistentVolumeClaim (PVC) work?

A PersistentVolumeClaim (PVC) is a request for storage by a pod. It asks for a certain size and access mode, and Kubernetes matches it to a suitable PersistentVolume.

beginner

What happens if you don’t use persistent storage for stateful apps in Kubernetes?

If you don’t use persistent storage, any data created by the app will be lost when pods restart or move, causing loss of user data or app state.

What does persistent storage in Kubernetes help with?

A Making pods run faster

B Keeping data safe when pods restart or move

C Increasing CPU power for pods

D Automatically scaling pods

Persistent storage keeps data safe even if pods restart or move, preventing data loss.

Which Kubernetes object represents a storage resource in the cluster?

A ConfigMap

B Pod

C Service

D PersistentVolume (PV)

PersistentVolume (PV) represents a storage resource available in the cluster.

What does a PersistentVolumeClaim (PVC) do?

A Requests storage for a pod

B Deletes storage

C Creates a new pod

D Monitors pod health

A PVC requests storage from available PersistentVolumes for a pod to use.

What happens to data if a pod without persistent storage restarts?

A Data is saved automatically

B Pod restarts faster

C Data is lost

D Pod scales up

Without persistent storage, data inside the pod is lost when it restarts.

Why is persistent storage important for stateful applications?

A To keep user data safe across pod restarts

B To speed up network traffic

C To reduce memory usage

D To increase CPU cores

Stateful apps need persistent storage to keep user data safe even if pods restart.

Explain why persistent storage is important in Kubernetes and how it helps pods.

Think about what happens to data when pods restart or move.

Describe the roles of PersistentVolume and PersistentVolumeClaim in Kubernetes storage.

One is the storage itself, the other asks for storage.

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