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

Autopilot Scheduler

Applies an Autopilot preset on a cron schedule, so replicas are ready before a known peak and return to the default after it.

The challenge

Logins peak at 9:00: HPA takes 30+ seconds to go from 10 to 80 Pods

kubernetes.io, Horizontal Pod Autoscaling; Google Cloud and The Harris Poll, 2019. The 9:00 peak and Pod counts are illustrative.

HPA scales on the load it sees now. When everyone logs in at 9:00, it starts adding Pods only after the load arrives.

With default settings, HPA can at most double the Pods every 15 seconds. From 10 Pods, reaching 80 takes three increases, the last one 30 seconds after the first.

Known peaks still cause outages: 10% of retail executives said their website went down during Black Friday or Cyber Monday the year before (Google Cloud and The Harris Poll, 2019).

Replicas lag the peak, then are ready before itWithout WaveWith WavePods too latePods ready early
Without Wave
Replicas start to grow only after the 9 a.m. peak arrivesloadreplicastoo few Podsmin 1006:0008:0010:0012:00
HPA starts after the load arrives. With default settings, from 10 Pods it can at most double the Pods every 15 seconds.
With Wave
A scheduled preset raises min replicas before the peakloadreplicaspreset: min 80starts 10 min early06:0008:0010:0012:00
A cron schedule applies an Autopilot preset with min 80 replicas 10 minutes before 9 a.m., then returns to the default after its duration.

Times and Pod counts are illustrative, and the timing is not to scale. HPA scale-up default (100% or 4 Pods per 15s, whichever is more): kubernetes.io. Presets and pre-execution: Autopilot Scheduler docs.

How Wave does it

Getting Pods ready for a known 9:00 peak
HPA alone (default)Ready after the peak starts
  1. Load arrives
    everyone logs in at 9:00
  2. ↓every 15s→
    HPA controller
    sees the load only after it arrives
  3. ↓up to 2x / 15s→
    Deployment
    10 Pods, then 20, 40, 80
  4. ↓Pod startup→
    Pods ready
    after the peak has started
Wave Autopilot SchedulerReady before the peak
  1. Schedule
    cron in UTC: 50 8 * * 1-5
  2. ↓starts early→
    Wave Core
    applies the Autopilot preset 10 minutes early (pre-execution)
  3. ↓min 80→
    Kubernetes API
    raises the replicas to 80
  4. ↓before 9:00→
    Deployment
    80 Pods ready; back to the default after the duration
HPA scale-up default: kubernetes.io. Schedules, presets, pre-execution, and UTC cron: Autopilot Scheduler docs. Times and Pod counts are illustrative.
1

Choose a preset

An Autopilot preset sets the strategy, thresholds, and min/max replicas, for example min 80 for the morning peak.

2

Set a cron schedule

Pick the Deployments and a cron expression in UTC. Add a year for a one-time event such as a campaign launch.

3

Start early, then return

Pre-execution starts the preset minutes before the peak. When the duration ends, the Deployments return to their default config.

Related in Wave Autoscale

Autopilot →Min/Max Recommendation →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