From 57e72bce9ae306eeda54050c0fed5899d9733057 Mon Sep 17 00:00:00 2001 From: Matthew Cary Date: Mon, 13 Dec 2021 10:14:08 -0800 Subject: [PATCH] Clarify editing PV for volume resize --- content/en/docs/concepts/storage/persistent-volumes.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/en/docs/concepts/storage/persistent-volumes.md b/content/en/docs/concepts/storage/persistent-volumes.md index 1a887fcb38..241f05b5cc 100644 --- a/content/en/docs/concepts/storage/persistent-volumes.md +++ b/content/en/docs/concepts/storage/persistent-volumes.md @@ -254,6 +254,13 @@ To request a larger volume for a PVC, edit the PVC object and specify a larger size. This triggers expansion of the volume that backs the underlying PersistentVolume. A new PersistentVolume is never created to satisfy the claim. Instead, an existing volume is resized. +{{< warning >}} +Editing the size of a PersistentVolume can prevent resize of the volume. If the +capacity of a PersistentVolume edited, then the PersistentVolumeClaim size is edited to increase to +the same value, no resize will happen. Kubernetes will think the backing volume has been manually +increased and that no resize is necessary. +{{< /warning >}} + #### CSI Volume expansion {{< feature-state for_k8s_version="v1.16" state="beta" >}}