compute

POST /v1/compute/clusters

Create a k3s cluster, optionally with Argo CD.

All compute endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the billing.payment.manage permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/compute/clusters \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "name": <string>, "zone": <string>, "plan_code": <string>, "image": <string>, "worker_count": <integer> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

202. One control-plane machine and worker_count workers, each an ordinary pay-by-the-hour server, built into a private network. Kubernetes comes from the k3s stable channel and Argo CD from its stable manifests; the versions actually installed are read back from the cluster. ⛔ The balance must cover every machine's runway before anything is built. Quote it first with quoteComputeCluster. Requires billing.payment.manage.

Request body

NameTypeRequiredWhat it is
namestringYes—
zonestringYes—
plan_codestringYes—
imagestringYes—
worker_countintegerYes—
install_argocdbooleanNo—
deploy_sample_appbooleanNoDeploy Argo CD's example application through Argo CD. Needs Argo CD.
ssh_keysstring[]NoThe ids of the authorised keys every node gets, from listComputeSshKeys. Every id must be one of the ordering organisation's own registered keys (listComputeSshKeys for that…
org_idUuid | nullNo—

Response

NameTypeRequiredWhat it is
idUuidYesUUIDv7 identifier — sortable by creation time (docs/02 §8).
namestringYes—
deploy_targetstringYes—
zonestringYes—
plan_codestringYes—
imagestringYes—
worker_countintegerYes—
install_argocdbooleanYes—
deploy_sample_appbooleanYes—
statusstring<pending, provisioning, bootstrapping, ready, failed, terminating, terminated>Yes—
messagestringYes—
kubernetes_versionstringYes—
argocd_versionstringYes—
ready_nodesintegerYes—
sample_app_healthstringYesArgo CD's sync/health for the sample application, e.g. Synced/Healthy.
api_addressstringYesThe Kubernetes API's public address (port 6443).
network_idstringYes—
nodesComputeServer[]Yes—
created_atstringYes—
ready_atobjectYes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503