PV Auto-Expansion
Wave grows a PVC when its usage reaches the threshold you set, by a percentage or a fixed size, up to an optional max capacity.
The PVC reaches 100%, and Kubernetes waits for someone to edit its size
kubernetes.io, Persistent Volumes; Wave Auto Expansion docs. 80%, +50%, and 10 GiB are docs examples and are illustrative here.
Kubernetes grows a volume only when someone asks: "To request a larger volume for a PVC, edit the PVC object and specify a larger size." It works only if the StorageClass sets allowVolumeExpansion to true (kubernetes.io).
Nothing in Kubernetes watches usage and edits the PVC for you. And "Kubernetes does not support shrinking a PVC to less than its current size" (kubernetes.io), so any automatic growth needs a limit.
Editing the PVC to grow it: kubernetes.io, Persistent Volumes. 80%, +50%, and 10 to 15 to 22.5 GiB: Wave Auto Expansion docs example. The usage curve and the 30 GiB max are illustrative.
How Wave does it
- PVCthe app keeps writing
- no checkSomeonenotices the volume is full
- editsPVC speca larger storage request
- resizeVolumegrows if the StorageClass allows it
- Wave Corechecks usage every few minutes
- triggerYour rule+% or a fixed size, optional max
- new sizeStorageClassmust allow volume expansion
- updatePVCtracked to Completed or a failure status
Set a threshold per PVC
In the console, or as a WavePvcAutoExpansion Custom Resource, set the usage percentage that starts an expansion, for example 80%. The threshold has no default, so you choose it for each PVC.
Choose how much to grow
Grow by a percentage of the current size, such as 10 GiB to 15 GiB at 50%, or by a fixed size. An optional Max Capacity sets the ceiling, and Wave trims the last step so it lands exactly on it.
Follow every attempt
Wave checks that the StorageClass allows expansion, then updates the PVC. The logs show InProgress, Completed, or a failure such as ExpansionFailed or MaxCapacityReached. Some storage providers need a Pod restart or downtime to finish the resize.