Why persistent storage matters in Kubernetes - Why It Works

Introduction

Kubernetes runs applications in containers that can be stopped or moved anytime. Without persistent storage, any data saved inside a container is lost when the container stops. Persistent storage keeps data safe even if containers restart or move to other servers.

When you run a database in Kubernetes and want to keep its data safe after restarts.

When your app needs to save user files or uploads that must not disappear.

When you want to keep logs or reports generated by your app for later use.

When you want to share files between multiple containers running together.

When you want to upgrade or restart your app without losing its data.

Config File - persistent-volume-claim.yaml

persistent-volume-claim.yaml

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: example-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
  storageClassName: standard

This file creates a PersistentVolumeClaim (PVC) named example-pvc. It requests 1 gigabyte of storage that can be read and written by one node at a time. The storageClassName tells Kubernetes which storage type to use, here the default standard class.

The PVC lets your app ask Kubernetes for storage that stays safe even if the app restarts or moves.

Commands

This command tells Kubernetes to create the PersistentVolumeClaim defined in the file. It reserves storage for your app to use persistently.

Terminal

kubectl apply -f persistent-volume-claim.yaml

Expected Output

persistentvolumeclaim/example-pvc created

This command checks the status of the PersistentVolumeClaim to see if the storage is ready to use.

Terminal

kubectl get pvc example-pvc

Expected Output

NAME          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE

example-pvc   Bound    pvc-12345678-90ab-cdef-1234-567890abcdef   1Gi        RWO            standard       10s

This command shows detailed information about the PersistentVolumeClaim, including which storage volume it is using and its status.

Terminal

kubectl describe pvc example-pvc

Expected Output

Name:          example-pvc

Namespace:     default

StorageClass:  standard

Status:        Bound

Volume:        pvc-12345678-90ab-cdef-1234-567890abcdef

Labels:        <none>

Annotations:   <none>

Finalizers:    [kubernetes.io/pvc-protection]

Capacity:      1Gi

Access Modes:  RWO

Events:        <none>

Key Concept

Persistent storage in Kubernetes keeps your data safe and available even when containers stop, restart, or move.

Common Mistakes

Not creating a PersistentVolumeClaim before using storage in a pod.

Without a PVC, the pod has no guaranteed storage, so data will be lost when the pod restarts.

Always create and bind a PersistentVolumeClaim before mounting storage in your pod.

Using emptyDir volumes for data that must persist.

emptyDir storage is deleted when the pod stops, so data is lost.

Use PersistentVolumeClaims for any data that needs to survive pod restarts.

Summary

Create a PersistentVolumeClaim to reserve persistent storage in Kubernetes.

Check the PVC status to ensure storage is ready before using it.

Use persistent storage to keep data safe even if containers restart or move.

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