whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update content/en/docs/concepts/storage/persistent-volumes.md

Browse Source 
Co-authored-by: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
Matt Cary
2021-12-13 15:35:11 -08:00
committed by GitHub
parent 57e72bce9a
commit 33aae9b7e5
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/storage/persistent-volumes.md
+6 -3
View File
@@ -255,9 +255,12 @@ size. This triggers expansion of the volume that backs the underlying Persistent
new PersistentVolume is never created to satisfy the claim. Instead, an existing volume is resized. new PersistentVolume is never created to satisfy the claim. Instead, an existing volume is resized.
{{< warning >}} {{< warning >}}
Editing the size of a PersistentVolume can prevent resize of the volume. If the Directly editing the size of a PersistentVolume can prevent an automatic resize of that volume.
capacity of a PersistentVolume edited, then the PersistentVolumeClaim size is edited to increase to If you edit the capacity of a PersistentVolume, and then edit the `.spec` of a matching
the same value, no resize will happen. Kubernetes will think the backing volume has been manually PersistentVolumeClaim to make the size of the PersistentVolumeClaim match the PersistentVolume,
then no storage resize happens.
The Kubernetes control plane will see that the desired state of both resources matches,
conclude that the backing volume size has been manually
increased and that no resize is necessary. increased and that no resize is necessary.
{{< /warning >}} {{< /warning >}}