World map

 

BM: Baca dalam Bahasa Melayu

World K4: Notes, Lockers & Packages

StorageClass and access modes

You will learn: who builds lockers on demand, and who may open a locker at once.

Checked with Kubernetes 1.37 on 31 Oct 2026

The problem

You are here: cluster kind-dev namespace default
kubectl get pv lists one volume named pvc- and a long id, 1Gi, RWO, Bound to default/orders. Terminal output: $ kubectl get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS VOLUMEATTRIBUTESCLASS REASON AGE pvc-14148d20-7191-41bd-b0ee-9b62e9454543 1Gi RWO Delete Bound default/orders standard <unset> 14s

Last lesson, a locker appeared by itself. Its name is pvc- plus a long id. Nobody wrote its YAML. So who built it?

Try it

Find the locker maker. Then ask the waiting claim what it is doing.

You are here: cluster kind-dev namespace default
Stalls: 3. Trays: 0 (0 ready). Waiting for a stall: 0.
dev-control-planeOpenManager

No trays here.

dev-workerOpen

No trays here.

dev-worker2Open

No trays here.

Time: +0s (sped up)

Watch

Put the locker-building steps in order, first at the top.

First step at the top. Put these in order. Use the arrows, or drag.

  • The claim turns Bound
  • The provisioner builds a PV on that stall
  • A pod that uses the claim lands on a stall
  • You apply a claim. It is Pending.
  • The pod starts, with the locker mounted

The maker is a StorageClass: The locker maker: it builds a new PV when a claim asks for one.. kind’s standard class builds each PV on the stall where the pod runs.

Predict

A claim asks for storageClassName: fast. This cluster has no class called fast. What happens?

Pick one answer.

Watch

Drag a card into a box. Or tap the card, then tap the box.

        An access mode: Who may use a locker at once: one node (RWO), many nodes (RWX), many readers (ROX) or one pod (RWOP). says who may use the locker at once. Not every StorageClass offers every mode.

        Predict

        Three trays on three stalls must all save photos to one folder. Which mode?

        Pick one answer.

        Try it

        This claim is refused. Fix the size.

        Fix the manifest, then press Apply.

        claim.yaml11 lines

        You did it!

        You can now explain StorageClasses and pick an access mode.

        Go deeper (optional)

        WaitForFirstConsumer waits for a pod, so the PV lands where the pod runs. Immediate builds it at once. allowVolumeExpansion: true lets a claim grow later. Clouds offer classes like fast SSDs or network file storage.

        Real rep (optional), on a practice kind cluster:

        Real mission

        1. kubectl get storageclass
        2. kubectl get storageclass standard -o yaml
        3. kubectl describe pvc orders
        4. kubectl delete pvc orders

        0 of 4 steps done · Your ticks are saved.