study.

StorageClasses and Reclaim Policies · CKA

Understand how storage is provisioned and what happens after it is released.

← CKA

Learn with progress and quizzes

First, understand the concepts.

StorageClass

Settings such as provisioner, parameters, reclaimPolicy, and volumeBindingMode define dynamic storage behavior.

Retain and Delete

Retain requires manual handling of a volume after its claim is removed. Delete removes the PV and the external storage asset where supported.

Why it matters

Deleting a PVC can lead to deletion of the underlying disk. Distinguish StorageClass defaults from an existing PV’s actual settings.

Work through the reasoning

Separate creation policy from resources

A StorageClass defines provisioning behavior, binding mode, and defaults. Read reclaimPolicy on an existing PV directly; changing the class does not imply that existing PV policy changed.

Understand responsibility after Retain

Retain leaves storage after its claim is removed, requiring a separate cleanup and reuse procedure. Delete can remove underlying storage with a supporting provisioner. Restrict deletion experiments to disposable data.

Learn by doing.

You need kubectl and access to your own practice Kubernetes cluster. Each lab is independent. Check your current context first, then run the commands in your own terminal.

Read the reclaim policies in your StorageClass and PV YAML. Do not delete resources for this exercise.

kubectl get storageclass -o yaml
kubectl get pv -o yaml
kubectl explain storageclass.reclaimPolicy

How to check your result

Explain how reclaim policies affect actual data, and note which fields you would check before deleting a claim.

Apply what you learned

Which three things should you check before deleting a PVC containing production data?

Reveal the reasoning after trying

Check the bound PV’s current reclaim policy, the real storage identifier and ownership, and a recoverable backup. This lesson uses inspection; do not delete important volumes to test the policy.

Ready to check your understanding?

Which policy leaves a released volume for manual handling?

  1. Delete
  2. Retain
  3. Restart
  4. RecycleAlways
Reveal the reasoning after trying

Retain

Retain requires an administrator to reclaim the volume manually instead of automatically deleting it.

Kubernetes documentation