StorageClasses and Dynamic Provisioning

Storage / Guide 68 of 103 / Intermediate

• Kubernetes1.36.4
• Cluster4 nodes
• Runtimecontainerd 2.2.6
• CNICalico v3.32.1
• TimeAbout 30 min

local-path is a node-local provisioner. A cloud or network provisioner behaves the same at the API level and differs in what the volume actually is.

• Provisionerrancher.io/local-path

This guide includes

Use this when nobody should be hand-creating volumes any more. This matters because a claim against a WaitForFirstConsumer class is supposed to sit Pending until a Pod appears - and that Pending looks exactly like a broken cluster.

• reading the four StorageClass fields that decide how every claim against it behaves
• seeing Pending as the correct answer here, with the event that explains why
• creating a Pod and watching scheduling, provisioning and binding all resolve at once
• deleting the Pod and confirming the data outlives it

Before you start

• The PersistentVolumes and claims guide, since this replaces the manual half of it.
• A cluster with a working provisioner and a default StorageClass. The installation guides add local-path.
• The node affinity guide, for reading the affinity the generated volume carries.

1. 1

   Read the StorageClass before using it

2. 2

   Pending is the correct answer, and the event says so

3. 3

   A Pod appears and the volume is created where it landed

4. 4

   The data outlives the Pod

Official sources

• Storage Classes
• Dynamic volume provisioning
• Volume binding mode
• Change the default StorageClass
• Expanding persistent volumes claims
• local-path-provisioner