Hanzo

K8s

Package visor is the compute you rent from Hanzo: machines, GPUs and clusters — launch one, resize it, tear it down.

Package visor is the compute you rent from Hanzo: machines, GPUs and clusters — launch one, resize it, tear it down.

Base URLhttps://api.hanzo.ai
Operations5
AuthAuthorization: Bearer $HANZO_API_KEY

k8s

GET /v1/k8s/clusters/{id}

Returns one cluster's detail: node pools + worker nodes. Visor scopes the lookup to the org (a foreign or missing id resolves to not-found), so a tenant can never read another tenant's cluster by guessing an id.

ParameterInTypeRequiredDescription
idpathstringyesID is the provider's DOKS cluster id. Visor scopes the lookup to the caller's org, so another tenant's id resolves to…

DELETE /v1/k8s/clusters/{id}

Destroys a DOKS cluster by id and answers 204. ADMIN-GATED, like create. Visor scopes the delete to the org (refuses a foreign id), so this can only ever remove the caller org's own cluster.

ParameterInTypeRequiredDescription
idpathstringyesID is the provider's DOKS cluster id. Visor scopes the lookup to the caller's org, so another tenant's id resolves to…

GET /v1/k8s/clusters

Lists the org's DOKS clusters (Visor, house account) folded with the org's BYO clusters — ONE fleet cluster view under the unified k8s noun. A Visor outage is logged and skipped so a down optional provider never hides the BYO list.

POST /v1/k8s/clusters

Provisions a DOKS cluster for the caller's org and answers 201. ADMIN-GATED — a SuperAdmin, or an OrgAdmin of the caller's own org — because provisioning spends real infrastructure on the house account. The request is validated at this boundary, then Visor owns provisioning and the hanzo-org ownership tag.

Request bodyapplication/json (required)

FieldTypeRequiredDescription
namestringName is the cluster's name.
nodePoolobject
regionstringRegion is the provider region slug (e.g.
versionstringVersion is the Kubernetes version slug; empty takes the provider default.

GET /v1/k8s/nodes

Returns every DOKS worker node in the org's clusters as a machine — the SAME set the fleet folds in (managedMachines), exposed directly under the k8s noun. House account (hanzo-org cluster tag) + BYOC, deduped by Visor.


All Hanzo APIs · Interactive reference

How is this guide?

On this page