Update cluster
PATCH /tenants/{tenant}/clusters/{name}
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
required
string
Tenant name
name
required
string
Cluster name
Header Parameters
Section titled “Header Parameters ” If-Match
string
ETag for optimistic locking
Request Body
Section titled “Request Body ”Fields to update (at least one required)
object
alerts
Updated alert configuration
object
key
additional properties
resources
Updated resource allocations
object
cpu
string
Example
4 memory
string
Example
16Gi storage
string
Example
100Gi version
Target Kubernetes version for upgrade
string
Example
1.33Responses
Section titled “ Responses ”Updated cluster
object
alerts
object
key
additional properties
createdAt
string
Example
2026-02-01T14:00:00Z displayName
string
Example
Production Cluster name
string
Example
production resourceVersion
string
Example
294810 resources
object
cpu
string
Example
4 memory
string
Example
16Gi storage
string
Example
100Gi status
object
conditions
Array<object>
object
key
additional properties
endpoint
string
Example
https://production.acme.kupe.cloud kubernetesVersion
string
Example
v1.32.3 metrics
object
key
additional properties
phase
string
Example
Running type
string
Example
dedicated version
string
Example
1.32Headers
Section titled “Headers ” ETag
string
New resource version
Validation error
object
error
string
Missing or invalid authentication
object
error
string
Admin access required
object
error
string
Cluster not found
object
error
string
ETag mismatch
object
error
string
Rate limit exceeded
object
error
string