Skip to main content
GET
Global Cluster Status
Minimum role: viewer. Takes no parameters. The endpoint lists every ClusterRegistration in every namespace and counts:
  • totalClusters: all registrations
  • healthyClusters: connected registrations (status.connected: true) whose Degraded condition is not True
  • degradedClusters: connected registrations whose Degraded condition is True (some nodes are not Ready)
  • offlineClusters: registrations that are not connected
clusters holds each registration with the fields described in List Clusters; it is null when there are no registrations. There are no node, resource, SLO or incident aggregates here; for issue totals use Federation Status.

Authorizations

X-API-Key
string
header
required

API key sent in the X-API-Key header. Keys are read from the Secret chatcli-operator-secrets, key api-keys (fallback: ConfigMap chatcli-operator-config, key api-keys) in the operator namespace, as a YAML list of {key, role, name, description} (name is the identity recorded on approval decisions); the operator chart creates it only with apiKeys.create: true. Roles: viewer < operator < admin — any other role string is denied everywhere. Changes are picked up within about 30 seconds; deleting both the Secret and the ConfigMap revokes every key. With no keys configured every /api/ call returns 401, unless CHATCLI_OPERATOR_DEV_MODE=true, which grants admin without a key (development only).

Response

Global status

apiVersion
string
Example:

"v1"

kind
string
Example:

"GlobalClusterStatus"

spec
object