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

Karpenter Dashboard

Shows every Karpenter NodePool on one screen in Wave Console: nodes, cost per hour, Spot ratio, disruptions, and thrashing alerts.

The challenge

A NodePool creates and removes 6 nodes in one hour, and no screen shows why

The 6 nodes are illustrative. karpenter.sh v1.14 docs: Metrics, Disruption, Getting Started with Karpenter.

By default, Karpenter reports its state as Prometheus metrics and Kubernetes events. Its getting-started Grafana stack does not include the persistent storage that monitoring a production deployment needs (karpenter.sh).

Karpenter resets the consolidation timer whenever a Pod is added to or removed from a node (karpenter.sh). When nodes are created and removed again and again, the reason is spread over NodeClaims, events, metrics, and the AWS bill.

6 nodes come and go in one hour, and Wave flags the thrashingWithout WaveWith Wave6 nodes, no reasonthrashing flagged
Without Wave
A NodePool creates and removes 6 nodes in one hour, and the reason is in 4 places0 min30 min60 minNodeClaimsEventsMetricsAWS bill4 places, joined by hand
By default, Karpenter reports what it does as Prometheus metrics and Kubernetes events. To see why 6 nodes came and went in one hour, you join NodeClaims, events, metrics, and the AWS bill by hand.
With Wave
Wave shows the 6 short-lived nodes as one thrashing alert0 min30 min60 minThrashing Pattern6 nodes affected, average lifespan 8 min
Wave shows the same hour in Karpenter > Overview. A Thrashing Pattern alert lists the affected nodes, the reason, their average lifespan, and the average Pods affected.

The 6 nodes and their lifespans are illustrative. Metrics and events: karpenter.sh v1.14 docs. The Thrashing Pattern alert and its fields: Wave Karpenter Dashboard docs.

How Wave does it

From node changes to a reason you can read
Karpenter by defaultSpread over tools
  1. Karpenter
    creates and removes NodeClaims
  2. ↓exports→
    Prometheus
    metrics in Prometheus format
  3. ↓charts→
    Grafana
    example dashboards, no persistent storage
  4. ↓you join→
    Engineer
    matches metrics, events, and the AWS bill by hand
Wave Karpenter DashboardOne screen
  1. Wave Agent
    reads nodes, NodePools, and NodeClaims
  2. ↓gRPC→
    Wave Core
    processes the Karpenter data
  3. ↓checks→
    Thrashing check
    nodes created and removed in rapid succession
  4. ↓alerts→
    Wave Console
    Karpenter > Overview: nodes, cost per hour, Spot ratio, alerts
Prometheus metrics and the getting-started Grafana dashboards: karpenter.sh v1.14 docs. Wave Agent over gRPC, Wave Core, thrashing detection, and the Karpenter Overview page: Wave Karpenter docs.
1

Collect from Karpenter

The Wave Agent sends node, NodePool, and NodeClaim data to Wave Core over gRPC. It needs Amazon EKS, Karpenter v0.32 or later, and one Helm value, karpenter.enabled.

2

See cost and Spot in one place

Karpenter > Overview in Wave Console shows Karpenter nodes, total cost per hour, Spot ratio, active NodePools, and Spot interruptions. Each NodePool shows its disruptions and thrashing over 30 days.

3

Catch thrashing

Wave flags nodes that are created and removed in rapid succession. The Thrashing Pattern alert shows the affected nodes, the reason, their average lifespan, and the average Pods affected.

4

Look into one NodePool

Each NodePool has a node lifecycle timeline, its NodeClaims with their conditions and cost per hour, and its disruption events.

Related in Wave Karpenter

Node Warmup →Spot Workload Placement →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