Storage classes for dynamic provisioning in Kubernetes - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a StorageClass in Kubernetes?

A StorageClass defines how a unit of storage is dynamically provisioned in Kubernetes. It specifies the type of storage (like SSD or HDD), the provisioner, and parameters for creating persistent volumes automatically.

beginner

How does dynamic provisioning work with StorageClasses?

When a PersistentVolumeClaim requests storage with a StorageClass, Kubernetes uses the StorageClass's provisioner to create a PersistentVolume automatically without manual admin intervention.

intermediate

What key fields are defined in a StorageClass YAML?

Key fields include: <br> - provisioner: the plugin that creates storage<br> - parameters: settings for the storage<br> - reclaimPolicy: what happens to storage after release<br> - volumeBindingMode: when volume binding happens

intermediate

What is the purpose of the reclaimPolicy in a StorageClass?

The reclaimPolicy tells Kubernetes what to do with the storage after the PersistentVolumeClaim is deleted. Common values are Delete (storage is deleted) or Retain (storage is kept for manual cleanup).

beginner

Give an example of a common provisioner used in StorageClasses.

A common provisioner is kubernetes.io/aws-ebs for AWS Elastic Block Store, or kubernetes.io/gce-pd for Google Cloud Persistent Disk. These provisioners create cloud storage volumes dynamically.

What does a StorageClass in Kubernetes define?

A Network policies for pods

B User permissions for storage access

C How storage volumes are dynamically created

D Container image versions

A StorageClass defines how storage volumes are dynamically provisioned in Kubernetes.

Which field in a StorageClass specifies the plugin to create storage?

A parameters

B reclaimPolicy

C volumeBindingMode

D provisioner

The provisioner field specifies the plugin that creates the storage volume.

What happens if reclaimPolicy is set to Delete?

A Storage volume is kept after claim deletion

B Storage volume is deleted after claim deletion

C Storage volume is backed up automatically

D Storage volume is resized automatically

Delete means the storage volume is deleted when the PersistentVolumeClaim is deleted.

Dynamic provisioning eliminates the need for:

A Manual creation of PersistentVolumes

B Using PersistentVolumeClaims

C Defining StorageClasses

D Pod scheduling

Dynamic provisioning automatically creates PersistentVolumes, so admins don't create them manually.

Which of these is NOT a typical parameter in a StorageClass?

A pod CPU limits

B type of disk (SSD/HDD)

C provisioner plugin name

D reclaim policy

Pod CPU limits are unrelated to StorageClass parameters.

Explain how StorageClasses enable dynamic provisioning in Kubernetes.

Think about how storage is created automatically when requested.

Describe the role of reclaimPolicy in a StorageClass and its common values.

Consider what happens to storage after you stop using it.