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

Idle Node Detection

Finds nodes that run only DaemonSet Pods, with no application Pod for about a week, and shows the CPU and memory they hold.

The challenge

A node runs only DaemonSet Pods for 1 week and still costs full price

kubernetes.io, DaemonSet; Cluster Autoscaler FAQ (kubernetes/autoscaler on GitHub); Datadog State of Cloud Costs, 2024. The 1-week span is illustrative.

A DaemonSet ensures that all (or some) nodes run a copy of a Pod (kubernetes.io). So a node with no application Pod still runs node-exporter, fluentd, or calico-node. Kubernetes does not mark that node idle, and the cloud provider bills it like any other node.

Cluster Autoscaler considers a node for removal only when the Pod requests on it are below 50% of its allocatable, and it counts DaemonSet Pods in that sum by default. It does not scale down a node group that is already at its minimum size (Cluster Autoscaler FAQ).

83% of container costs are associated with idle resources, and about 54% of that wasted spend is cluster idle, the cost of overprovisioning cluster infrastructure (Datadog State of Cloud Costs, 2024).

A node with only DaemonSet Pods, then the same node marked IdleWithout WaveWith Wave$Idlebilled, not flaggedmarked Idle
Without Wave
node-4 runs only DaemonSet Pods, and nothing marks itnode-1node-2node-3node-4still billedApplication PodDaemonSet PodWhich node is doing no work?
node-4 runs only DaemonSet Pods. Cluster Autoscaler counts them toward its 50% check by default, and does not scale down a node group at its minimum size. Kubernetes shows node-4 as Ready, like the others.
With Wave
Wave marks node-4 Idle and shows its Pod Countnode-1node-2node-3node-4Idle · about a week3 total, 3 daemonsetApplication PodDaemonSet Pod
Wave sorts every Pod into system, DaemonSet, or application Pods. node-4 has had no application Pod for about a week, so Wave marks it Idle, with a Pod Count of 3 total, 3 daemonset.

Idle rule, about a week, and Pod Count: Wave Idle Node Detection docs. 50% check and minimum size: Cluster Autoscaler FAQ. The nodes and Pod counts are illustrative.

How Wave does it

From a node with no work to a list of idle nodes
Kubernetes by defaultNothing says the node is idle
  1. DaemonSet
    puts a Pod on every node, used or not
  2. ↓requests→
    Cluster Autoscaler
    counts DaemonSet Pods in its 50% check
  3. ↓min size→
    Node group
    at its minimum size, not scaled down
  4. ↓kept→
    Node
    stays Ready and billed, with no flag
Wave DiagnosisIdle nodes listed with their capacity
  1. Wave Agent
    reports the Pods on every node
  2. ↓gRPC→
    Wave Core
    sorts system, DaemonSet, and application Pods
  3. ↓classify→
    Idle window
    no application Pod for about a week
  4. ↓a week→
    Wave Console
    idle CPU and memory per cluster
Default lane: kubernetes.io (DaemonSet) and Cluster Autoscaler FAQ. Wave lane: Wave Idle Node Detection docs and Wave Architecture docs.
1

Sort every Pod

Wave sorts the Pods on each node into three groups: system Pods, DaemonSet Pods, and application Pods from Deployments, StatefulSets, and Jobs. One application Pod means the node is in use.

2

Wait out short states

A node is flagged only after it stays without application Pods for about a week by default. A scale-down delay or a batch Job that just finished does not flag it. A node that reads as completely empty is treated as a data gap, not as idle.

3

Show the waste

The Idle Nodes page shows the idle node count, idle CPU, and idle memory per cluster, and the Pod Count of each node by type. You decide what happens next: drain and delete the node, move workloads onto it, or keep it with the annotation waveautoscale.io/idle-node-detection="false".

Related in Wave Diagnosis

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