Update cluster API Reference
PATCH /tenants/{tenant}/clusters/{name}
Update mutable fields on a managed cluster. At least one field must be provided.
Changing version triggers a rolling Kubernetes upgrade. Changing resources adjusts the resource allocation for the cluster. Both operations are applied asynchronously.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Tenant name
Cluster name
Header Parameters
Section titled “Header Parameters ”ETag for optimistic locking
Request Body
Section titled “Request Body ”Fields to update (at least one required)
object
Updated alert configuration
object
HighAvailability is a create-time-only setting in v1. Both directions of the toggle are rejected on PATCH: false -> true is rejected with HA_ENABLE_ON_EXISTING_UNSUPPORTED; true -> false is rejected with HA_DISABLE_UNSUPPORTED. Tenants who want HA on an existing cluster recreate it as HA (blue-green swap).
Example
trueUpdated resource allocations
object
Example
4Example
16GiExample
100GiTarget Kubernetes version for upgrade
Example
1.33Responses
Section titled “ Responses ”Updated cluster
object
object
Example
2026-02-01T14:00:00ZExample
Production ClusterExample
trueExample
productionExample
294810object
Example
4Example
16GiExample
100Giobject
object
Example
https://production.acme.clusters.kupe.cloudHAConfigured is true once the operator has confirmed both 3/3 apiserver replicas AND 3/3 deployed-etcd replicas are Ready for the first time. Etcd readiness is required because in the OSS deployed-etcd path etcd runs in its own StatefulSet — quorum loss with healthy apiserver pods would block writes, so HA is not “operationally ready” until both tiers report 3/3.
Example
trueHAEnabledAt is the moment HAConfigured first became true and acts as the billing anchor. Stamped once, never updated, never cleared (v1 has no HA->single transition).
Example
2026-05-25T14:32:11ZHAEtcdReplicasDesired is the target HA etcd replica count (3 when HA is enabled, 0 otherwise).
Example
3HAEtcdReplicasReady is the count of deployed-etcd replicas currently Ready. Exposed separately from HAReplicasReady because in the OSS deployed-etcd path the etcd StatefulSet is independent of the apiserver StatefulSet, and etcd quorum loss with healthy CP can leave the cluster unable to serve writes.
Example
3HAPhase is the consumer-friendly HA rollup. One of pending, ha-healthy, ha-degraded, ha-unavailable. Empty for non-HA clusters.
Example
ha-healthyHAReplicasDesired is the target HA replica count (3 when HA is enabled, 0 otherwise).
Example
3HAReplicasReady is the count of HA control-plane (apiserver) replicas currently Ready.
Example
3Example
v1.32.3object
Example
RunningExample
sharedExample
1.32Warnings is an array of structured advisory messages. Always present (empty array when none). Populated today only by CREATE when a non-blocking advisory applies (e.g. HA_K8S_VERSION_RETIRING when HA is enabled on the oldest supported k8s minor). Each entry shares the same shape as a structured error envelope.
object
Example
HA_K8S_VERSION_RETIRINGExample
spec.highAvailabilityExample
Cluster's Kubernetes version (1.33) is approaching end-of-life on the current vCluster chart. Plan an upgrade before enabling HA.Example
warningHeaders
Section titled “Headers ”New resource version
Validation error
object
Missing or invalid authentication
object
Admin access required
object
Cluster not found
object
ETag mismatch
object
Rate limit exceeded