PV Capacity Forecast
Projects the usage of each PersistentVolume you choose at 7 and 30 days, next to its capacity, so you expand or clean up before it fills.
The database volume hits 100% at 2 a.m., and writes start to fail
kubernetes.io, Kubernetes Metrics Reference and Persistent Volumes; Wave PV Capacity Forecast docs. The 2 a.m. time is illustrative.
When a volume is full, writes fail, and a database can switch to read-only (Wave PV Capacity Forecast docs).
Kubernetes exposes volume usage as kubelet metrics, kubelet_volume_stats_used_bytes and kubelet_volume_stats_capacity_bytes, at stability level ALPHA (kubernetes.io). It does not watch them for you. You write the rule and pick the threshold.
A PVC can grow only if its StorageClass sets allowVolumeExpansion to true (kubernetes.io). Without it, you provision a larger volume and move the data.
Forecast per PV, the 7 and 30 day snapshots, and Used against Capacity: Wave PV Capacity Forecast docs. Writes fail on a full volume: Wave docs. The curve, 2 a.m., and the percentages are illustrative.
How Wave does it
- Applicationwrites data to its PVC
- writeskubeletreports volume used and capacity bytes
- metricsYour rulea threshold you write and maintain
- expandPVCgrows only if its StorageClass allows expansion
- Forecast toggleturned on per PV
- opt inWave Corekeeps at least 7 days of usage history
- trendForecastusage at 7 and 30 days
- per PVWave Consoleper-PV chart: Capacity vs Used
Pick the volumes
Forecasting is opt-in. Turn it on per PV with the On / Off toggle, for the volumes that matter, such as databases, Prometheus, or Loki.
Project usage
After at least 7 days of history, Wave shows the usage of each volume at 7 and 30 days, next to its capacity. The per-PV chart overlays the forecast on Used against Capacity. It shows no countdown; you judge the risk from the trend.
Expand in time
Grow the PVC by hand when its StorageClass allows expansion, or turn on PV Auto Expansion, which expands the volume when usage crosses your threshold.