Kubernetes PVC expansion: kubectl patch pvc

1) List your PVCs:

kubectl get pvc -A

NAMESPACE    NAME                                          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
dev          elasticsearch-master-elasticsearch-master-0   Bound    pvc-25c6e973-8fc4-463b-9288-123456678903   30Gi       RWO            standard       2y234d

2) Review your StorageClass has AllowVolumeExpansion configured to true.

kubectl describe sc standard | grep AllowVolumeExpansion
AllowVolumeExpansion:  True

3) Request new size

• kubectl -n your-namespace patch pvc your-pvc-name -p '{"spec":{"resources":{"requests":{"storage":"16Gi"}}}}'

4) Verify it

Related

• kubectl patch pvc
• FileSystemResizeSuccessful MountVolume.NodeExpandVolume succeeded for volume "pvc-678509b5-158b-11e9-8abc-1234567890"
• The PersistentVolumeClaim XXX is invalid

Activities

• Read https://www.gooksu.com/2022/08/how-to-increase-space-for-your-elasticsearch-instances-in-k8s-on-eck/
• Read https://www.percona.com/blog/percona-operator-volume-expansion-without-downtime/

See also

• Kubernetes Persistent Volume Claim (PVC) (kind: PersistentVolumeClaim), Kubernetes Persistent volumes (PV) (kind: PersistentVolume), kubectl describe pvc, kubectl get pvc, ClaimLost, ProvisioningSucceeded, PV access control
• Kubernetes storage, storage classes, PersistentVolume (PV), PVC, CSI, kind: StorageClass, kind: PersistentVolumeClaim, kind: PersistentVolume, kubectl [ get | describe | edit ] pvc, volumeClaimTemplates:, kubectl patch pv, FailedMount, Volume Expansion, Volume Cloning, snapshots, ExtraVolumes, NotTriggerScaleUp, volumePVCDataSource, AllowVolumeExpansion, EKS storage, provisioner, Storage Capacity Tracking, VolumeBinding, VolumeClaimTemplate, storage.k8s.io, CKA Storage, DoKC, EmptyDir, Volume populators, storageclass.kubernetes.io