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

NetFUNNEL Integration

Turns NetFUNNEL waiting-room segments ON when CPU, memory, or max replicas thresholds are exceeded, and OFF after a cooldown, so users wait in line instead of getting errors.

The challenge

Pods reach maxReplicas at 10, and new users get errors instead of a place in line

kubernetes.io, HorizontalPodAutoscaler v2 API reference and Horizontal Pod Autoscaling; Ticketmaster, statement on the Eras Tour presale, Nov 19, 2022. The 10 replicas are illustrative, from an example in the Wave NetFUNNEL Integration docs.

HPA cannot go past maxReplicas: "maxReplicas is the upper limit for the number of replicas to which the autoscaler can scale up" (kubernetes.io). Once a Deployment runs 10 of 10 replicas, every extra request goes to the same 10 Pods.

Below that limit, HPA adds replicas at most every 15 seconds (kubernetes.io). By default, nothing holds the users who arrive in between.

At Ticketmaster's 2022 presale, traffic reached 4x the previous peak, and Ticketmaster said it "had to slow down queues to keep them stable".

At 10 of 10 replicas users get errors, then they wait in lineWithout WaveWith Wave10/1010/10 Pods, errorsusers wait in line
Without Wave
Pods reach maxReplicas at 10, and new users get errorsTraffic spikeusers arrive faster than the Pods can serve themHPA at maxReplicasreplicas 10 / 10, HPA adds no more PodsEvery request goes innothing in front of the Pods holds users backUsers get errorsno place in line
With HPA alone, the Deployment stops at maxReplicas. Past that point, every new request goes to the same 10 Pods, and users get errors instead of a place in line.
With Wave
Wave turns NetFUNNEL segments ON, and users wait in lineThresholds exceededevery set rule, such as replicas 10 / 10Segments ONusers wait in line and see their positionUp to Max Inflow get inAutopilot scales the Pods, if it is onCooldown, then segments OFFafter the metrics drop, 60s by default, logged
When every set threshold is exceeded, Wave turns all mapped NetFUNNEL segments ON. Users wait and see their position, and each segment lets in up to its Max Inflow. After the metrics drop and the cooldown ends, Wave turns the segments OFF.

maxReplicas as the upper limit: kubernetes.io HPA reference. Segments ON and OFF, Max Inflow, and the 60s default cooldown: Wave NetFUNNEL Integration docs. The 10 replicas are illustrative, from a docs example.

How Wave does it

From a traffic spike to a waiting room
Kubernetes by defaultErrors, not a place in line
  1. HPA
    adds replicas at most every 15s
  2. ↓scales→
    Deployment
    stops at maxReplicas, 10 of 10
  3. ↓no queue→
    Ingress Gateway
    forwards every request; limits default to 2^32-1
  4. ↓all users→
    Pods
    take every request, and users get errors
Wave + NetFUNNELUsers wait in line, then get in
  1. Wave Metrics Agent
    collects CPU and memory per Deployment
  2. ↓checks→
    Wave
    every set threshold exceeded, such as replicas at max
  3. ↓turns ON→
    NetFUNNEL segment
    users wait and see their position; up to Max Inflow get in
  4. ↓while users wait→
    Autopilot
    scales the Pods if it is on; segments OFF after the cooldown, 60s by default
HPA: kubernetes.io. Istio defaults: istio.io DestinationRule reference. Wave: NetFUNNEL Integration docs; NetFUNNEL SaaS only. The 10 replicas are illustrative.
1

Connect your NetFUNNEL account

Enter the tenant ID and organization ID in Settings > NetFUNNEL in the Wave web console, or apply a WaveNetfunnelConnection. NetFUNNEL SaaS is the only supported type today.

2

Map a Deployment to segments

Pick the NetFUNNEL segments for a Deployment, an Argo Rollout, or a DeploymentConfig, and set CPU, memory, or max replicas thresholds and a cooldown. Wave Metrics Agent collects the CPU and memory data.

3

Wave turns the queue ON and OFF

When every set threshold is exceeded, Wave turns all mapped segments ON. Each segment lets in up to its Max Inflow, and the other users wait and see their position. After the metrics drop and the cooldown ends (60 seconds by default), Wave turns the segments OFF and logs each change.

Related in Wave Flow

Wave Flow →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