From c1d43465582b05bbbf4ab07002f6dc640c771022 Mon Sep 17 00:00:00 2001 From: Hemant Kumar Date: Mon, 25 Apr 2022 12:54:19 -0400 Subject: [PATCH] Update content/en/blog/_posts/2022-04-18-volume-expansion-ga.md Co-authored-by: Tim Bannister --- content/en/blog/_posts/2022-04-18-volume-expansion-ga.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md b/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md index dbd9f7e683..e5b2376c8e 100644 --- a/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md +++ b/content/en/blog/_posts/2022-04-18-volume-expansion-ga.md @@ -33,8 +33,9 @@ spec: storage: 1Gi # specify new size here ``` -Users can request expansion of the underlying volume by specifying a new value instead of old `1Gi` size. Once expansion is initiated - pvc's conditions can be monitored -for completion of volume expansion operation. +You can request expansion of the underlying PersistentVolume by specifying a new value instead of old `1Gi` size. +Once you've changed the requested size, watch the `status.conditions` field of the PVC to see if the +resize has completed. When Kubernetes starts expanding the volume - it will add `Resizing` condition to the PVC, which will be removed once expansion completes. More information about progress of expansion operation can also be obtained by monitoring events associated with the PVC: