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

Pod Scheduling Delay Detection

Records every Pod that waited in Pending, how long it waited, and each scheduler message behind the wait, and keeps them after Kubernetes deletes the events.

The challenge

A Pod waits in Pending, and its FailedScheduling event is gone after 1 hour

kubernetes.io, Debug Pods, Resource Management for Pods and Containers, and the kube-apiserver reference (--event-ttl, default 1h0m0s).

"If a Pod is stuck in Pending it means that it can not be scheduled onto a node" (kubernetes.io). The reason is in a FailedScheduling event, with a message such as "0/42 nodes available: insufficient cpu".

kube-apiserver keeps events for 1 hour by default (--event-ttl). A delay during the night leaves no reason behind by morning.

The event is gone after 1 hour; Wave keeps the wait and the reasonWithout WaveWith Wave12 minInsufficient cpuResolvedevent gone after 1hwait + reason kept
Without Wave
The reason for the wait is deleted 1 hour after it endsPod in Pending for 12 minFailedSchedulingdeleted after 1hyou check, 3h laterEvents: <none>0h1h2h3h4h
The Pod waits 12 minutes in Pending. The reason is in a FailedScheduling event, which kube-apiserver deletes 1 hour later by default. When you check 3 hours later, kubectl describe pod shows no events.
With Wave
Wave keeps the wait time and the reason for each Podapi-7f9cResolvedScheduling Delay12 minLatest Pod ConditionInsufficient cpuConditions history02:00 PodScheduled=False Unschedulable02:12 PodScheduled=TrueStill listed when you check, 3 hours later
Wave keeps a row for the Pod: 12 minutes of scheduling delay, the latest condition, Resolved, and the conditions history with each time.

Events kept 1 hour by default: kube-apiserver --event-ttl (kubernetes.io). The row and the conditions history: Wave Pod Scheduling Delay docs. The 12-minute wait, the times, and the 3-hour check are illustrative.

How Wave does it

From a Pending Pod to its reason
Kubernetes by defaultReason gone after 1 hour
  1. Pod
    created, phase Pending
  2. ↓schedule→
    kube-scheduler
    finds no node that fits
  3. ↓no fit→
    Event
    FailedScheduling, with the reason
  4. ↓1h TTL→
    kube-apiserver
    deletes events after 1 hour by default
Wave DiagnosisWait time and reason kept
  1. Wave Agent
    reports Pod state from every node
  2. ↓gRPC→
    Wave Core
    measures the time in Pending per Pod
  3. ↓per Pod→
    Conditions history
    every scheduler message, with its time
  4. ↓kept→
    Wave Console
    delays table, the last 7 days by default
Default lane: kubernetes.io (Pod Lifecycle, Resource Management for Pods and Containers, kube-apiserver --event-ttl). Wave lane: Wave Pod Scheduling Delay docs and Wave Architecture docs.
1

Measure the wait

Every delayed Pod gets a row with its scheduling delay, workload, namespace, and status, Resolved or Pending. KPI cards show total, average, resolved, and unresolved delays for the last 24 hours.

2

Keep the reason

The conditions history keeps every scheduler condition in order, with its time and message, such as "0/5 nodes are available: 2 Insufficient cpu". For Pods with a PVC, it also shows why the volume did not bind.

3

See when delays happen

An hourly chart of average pending time shows whether delays cluster around deploys or peak hours. The default range is the last 7 days.

Related in Wave Diagnosis

Pod / Container Failures →Memory Leak Detection →CPU Utilization Analysis →Idle Node Detection →Unused PV Detection →Cluster Resource Forecast →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