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

Cluster Resource Forecast

Projects the Pod CPU and memory requests of a cluster against node capacity, with snapshots at 7 and 30 days, so you can add nodes or cut requests in time.

The challenge

Requests reach 94% of node CPU, and the first warning is a Pending Pod

kubernetes.io, Reserve Compute Resources for System Daemons and Resource Management for Pods and Containers; Cluster Autoscaler FAQ; Wave Cluster Resource Forecast docs. 94% is the docs example and is illustrative here.

"The scheduler does not over-subscribe Allocatable" (kubernetes.io). When requests already take 94% of node CPU, the next Pods may not fit on any node. "If the scheduler cannot find any node where a Pod can fit, the Pod remains unscheduled until a place can be found" (kubernetes.io). The Pod stays Pending.

Cluster Autoscaler "periodically checks whether there are any pending pods" and then adds a node (Cluster Autoscaler FAQ). It acts after a Pod is already waiting.

Requests run into node CPU, then the same trend with a forecastWithout WaveWith Wavefirst sign: Pendingforecast to 30 days
Without Wave
Requests climb into node CPU, and a Pod waitsPod CPU RequestNode CPU: 100%94%Pod Pending-28dtoday+7d+30d
Pod CPU requests take 94% of node CPU today and keep climbing. Nothing shows the trend. The first sign is a Pod that stays Pending when no node has room.
With Wave
Wave draws the request trend forward, with 7 and 30 day snapshotsPod CPU RequestForecastNode CPU: 100%94%98%111%-28dtoday+7d+30d
Wave keeps the same history and draws the Pod CPU Request (Forecast) line: 98% at 7 days and 111% at 30 days. The line crosses node capacity between the two snapshots.

Forecast line and the 7 and 30 day snapshots: Wave Cluster Resource Forecast docs. 94% of node CPU: docs example. Pending when no node fits: kubernetes.io. The curve and the other values are illustrative.

How Wave does it

From growing requests to a forecast against capacity
Kubernetes by defaultFirst signal: a Pending Pod
  1. Pods
    each new Pod adds its requests
  2. ↓requests→
    Scheduler
    places a Pod only where Allocatable has room
  3. ↓no fit→
    Pod
    stays Pending with FailedScheduling
  4. ↓pending→
    Cluster Autoscaler
    adds a node after Pods are pending
Wave DiagnosisRequests vs capacity, 7 and 30 days out
  1. Wave Agent
    node capacity and Pod requests
  2. ↓gRPC→
    Wave Core
    keeps at least 7 days of history
  3. ↓trend→
    Forecast
    request trend at 7 and 30 days
  4. ↓to 30d→
    Wave Console
    forecast line against node capacity
Default lane: kubernetes.io (Reserve Compute Resources, Resource Management for Pods and Containers) and Cluster Autoscaler FAQ. Wave lane: Wave Cluster Resource Forecast docs and Wave Architecture docs.
1

Learn the trend

Wave needs at least 7 days of history. It tracks node CPU and memory capacity next to the Pod requests and limits in the cluster.

2

Project requests forward

The CPU and memory charts add a Pod CPU Request (Forecast) and a Pod Memory Request (Forecast) line, with snapshots at 7 and 30 days. Where a forecast line climbs toward the capacity line is roughly when you would run short. There is no countdown; you decide what is too close.

3

Pick the cheapest fix

Add nodes when the growth is real. When requests are inflated, cut them first with Smart Sizing, and the forecast drops without new hardware. A Filter Group narrows the forecast to a subset of workloads.

Related in Wave Diagnosis

Pod / Container Failures →Memory Leak Detection →Pod Scheduling Delay Detection →CPU Utilization Analysis →Idle Node Detection →Unused PV Detection →PV Capacity 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