PricingPricingDocsDocsBlogBlogBook a demoBook a demoCompanyCompany (opens in a new tab)
Product
DocsAPI ReferencePricingConsole DemoBlogCompany
Start Freev3.4.7
Platform & Observability

Programmable API

A REST API on Wave Core and 14 Custom Resource kinds, so a script or a Git repository can change Wave settings instead of the console.

The challenge

Turning on Autopilot for 40 Deployments means 40 trips through the console

Wave Architecture docs; Wave CRD Mode docs; Wave API reference (v3). The 40 Deployments are illustrative.

The console changes one workload at a time. To turn on Autopilot for 40 Deployments, someone opens each one, changes the setting, and saves it, 40 times.

Wave Core already serves a REST API on port 3024, "for Web Console and external integrations" (Wave Architecture docs). A script can make the same calls the console makes.

In CRD Mode, the settings live in Git as Custom Resources, so the same YAML applies to every cluster (Wave CRD Mode docs).

Toggles turned on one by one, then all at once by a scriptWithout WaveWith Wavecurl -X PUT40 dialogs1 script
Without Wave
Wave Console: one Deployment per dialogDeploymentsAutopilotprod/checkoutprod/paymentprod/cartprod/searchprod/orders+ 35 more Deployments40 dialogs, one Deployment at a time
In the console, Autopilot is turned on one Deployment at a time: open it, change the setting, save. For 40 Deployments, that is 40 passes.
With Wave
A script calls the Wave Core REST APIAPI=$WAVE/api/k8s/deploymentsfor d in $(cat deploys.txt); do curl -X PUT -d @on.json \ $API/prod/$d/autopilot-enableddoneprod/checkoutprod/payment+ 38 more, all On1 script: 40 PUT calls in one run
A script sends one PUT to the autopilot-enabled endpoint of each Deployment. All 40 change in one run, with no dialog.

Endpoint: Wave API reference (v3). REST API on Wave Core, port 3024: Wave Architecture docs. The 40 Deployments, their names, and the script are illustrative.

How Wave does it

From 40 dialogs to one script run
The console, by handOne Deployment per pass
  1. Wave Console
    pick the cluster, open the list
  2. ↓open→
    Deployment
    find it by name, open its page
  3. ↓edit→
    Autopilot
    turn it on in a dialog, then save
  4. ↓repeat→
    Next one
    back to the list, 39 to go
Wave REST API40 Deployments, one run
  1. Your script
    a CI job or a shell loop
  2. ↓PUT→
    Wave Core
    REST API on port 3024
  3. ↓applies→
    Deployment
    Autopilot on, as the console would set it
  4. ↓next→
    All 40
    changed in one run, no dialog
Default lane: the Wave Console, one dialog per Deployment. Wave lane: Wave Architecture docs (Wave Core REST API, port 3024) and the Wave API reference (autopilot-enabled). 40 is illustrative.
1

Call the REST API

The Wave API reference (v3) lists each endpoint with its parameters and responses. For example, one PUT call to the autopilot-enabled endpoint of a Deployment turns Autopilot on or off for that Deployment.

2

Or keep the settings in Git

In CRD Mode, 14 kinds of wavek8s.com Custom Resources hold the settings. You apply them with kubectl or ArgoCD, and Wave applies the same settings the console would. The console becomes read-only for those settings.

3

Check that it applied

Each Custom Resource reports a Synced condition in .status, with a reason such as AsExpected, TargetNotFound, or ValidationFailed. A target that does not exist yet is applied when it appears.

Related in Platform & Observability

SSO (OIDC) →PV Auto-Expansion →PV Cleanup →Alerts →Cluster Map →Prometheus & Grafana Integration →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