Expand a Hetzner Cloud volume

Confirm the class allows expansion

Expansion works only when the StorageClass sets allowVolumeExpansion: true. The standard class already does:

		$ kubectl get storageclass standard
NAME                 PROVISIONER         RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
standard (default)   csi.hetzner.cloud   Retain          WaitForFirstConsumer   true                   10d
	

If a custom class shows false in the ALLOWVOLUMEEXPANSION column, a PVC on it cannot be resized. Move the data to a class that allows expansion instead. See Migrate between storage classes .

Raise the storage request

Edit spec.resources.requests.storage on the PVC to the new, larger size. One field changes:

		spec:
  resources:
    requests:
      storage: 10Gi
      storage: 20Gi
	

A kubectl patch applies that same change in one line:

		$ kubectl patch pvc pv-claim -p '{"spec":{"resources":{"requests":{"storage":"20Gi"}}}}'
persistentvolumeclaim/pv-claim patched
	

kubectl edit pvc pv-claim opens the same field in an editor if you prefer to change it by hand.

Watch the capacity grow

The CAPACITY column in kubectl get pvc reports the volume's real size, so watch it climb to the new value:

		$ kubectl get pvc pv-claim
NAME       STATUS   VOLUME        CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS   AGE
pv-claim   Bound    pvc-8f3c...   20Gi       RWO            standard       <unset>                 5m
	

The capacity updates once both steps finish: the driver enlarges the Hetzner volume, then the filesystem grows to fill it. You never run a resize command inside the pod; the driver handles that part too.