clusters
Get a Cluster
GET
Get a Cluster
Headers
Response
The Cluster
provisioning: the hosted control plane starts. awaiting_node: join a server with a join token. awaiting_agent: install the agent (attached) or wait for it. configuring: the baseline is placed. disconnected: the agent stopped calling; workloads keep running.
Available options:
provisioning, awaiting_node, awaiting_agent, configuring, ready, degraded, disconnected, failed, deleting, deleted What needs attention now; empty when nothing does. Reasons:
agent-offline(warning): the agent is not connected; workloads keep running and nothing new rolls out until it reconnects.updater-behind(warning): the updater has run another release than the agent for 30 minutes, so no agent release is offered. Remedyrun-agent-installon an attached Cluster; none on a hosted one, whose agent and updater Akua re-applies.needs-customer-upgrade(warning): the offered agent release changes objects outside the access you granted, so it was not applied. Remedycustomer-upgradenames the missing permissions and thehelm upgradecommand.bundle-too-large(warning): the offered agent release is too large to deliver or to keep as a rollback copy, so it was not applied.update-rolled-back,baseline-degraded(warning): a capability release failed its health gate and was rolled back, or a capability is not healthy; see the Cluster’s capabilities. A list showsbaseline-degradedfrom the Cluster state only;update-rolled-backappears when the Cluster is read on its own.- When
stateisfailed, one error whose reason says why:control-plane-unready,enrollment-expired,agent-unsupported,baseline-failed,baseline-rollback-failed,cleanup-unconfirmed,node-removal-failedoragent-bundle-failed.
Maximum array length:
32Get a Cluster