PricingPricingDocsDocsBlogBlogBook a demoBook a demoCompanyCompany (opens in a new tab)
Product
DocsAPI ReferencePricingConsole DemoBlogCompany
Start Freev3.4.7
Wave Diagnosis

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 challenge

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.

A volume fills up, then the same trend with a forecastWithout WaveWith Wavefull at 2 a.m.forecast to 30 days
Without Wave
Used climbs into capacity, and writes fail at 2 a.m.UsedCapacity: 100%88%2 a.m.: writes fail-28dtoday+7d+30d
The volume is 88% full today and grows a little every day. Nothing projects it forward. It reaches 100% at 2 a.m. on day 19, and writes start to fail.
With Wave
Wave draws the usage trend forward, with 7 and 30 day snapshotsUsedForecastCapacity: 100%88%93%107%-28dtoday+7d+30d
Wave keeps the same history and draws the forecast: 93% at 7 days and 107% at 30 days. A forecast above 100% means the volume fills before that day.

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

From a filling volume to a forecast per PV
Kubernetes by defaultSeen at your threshold, or at 100%
  1. Application
    writes data to its PVC
  2. ↓writes→
    kubelet
    reports volume used and capacity bytes
  3. ↓metrics→
    Your rule
    a threshold you write and maintain
  4. ↓expand→
    PVC
    grows only if its StorageClass allows expansion
Wave DiagnosisUsage at 7 and 30 days, per PV
  1. Forecast toggle
    turned on per PV
  2. ↓opt in→
    Wave Core
    keeps at least 7 days of usage history
  3. ↓trend→
    Forecast
    usage at 7 and 30 days
  4. ↓per PV→
    Wave Console
    per-PV chart: Capacity vs Used
Default lane: kubernetes.io (Kubernetes Metrics Reference, Persistent Volumes). Wave lane: Wave PV Capacity Forecast docs.
1

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.

2

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.

3

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.

Related in Wave Diagnosis

Pod / Container Failures →Memory Leak Detection →Pod Scheduling Delay Detection →CPU Utilization Analysis →Idle Node Detection →Unused PV Detection →Cluster Resource Forecast →Read the docs →
Book a demoStart free
Product
Wave GPUAI Infrastructure Professional ServiceWaveWave AI Agent2026 Q4
Resources
DocsAPI ReferenceBlogConsole DemoPricing
Company
STCLabBook a demoContact
STCLab© 2026 Wave All rights reserved.
Terms of ServicePrivacy PolicyCookies