Skip to main content
GET
Federation Status
Minimum role: viewer. Takes no parameters. GET /api/v1/federation (no suffix) returns the same response.
  • totalClusters, connectedClusters, disconnectedClusters: from the status.connected field of every ClusterRegistration (a registration with no status counts as disconnected)
  • degradedClusters: connected registrations whose Degraded condition is True (some nodes are not Ready); they are also counted in connectedClusters
  • totalActiveIssues: Issues in this cluster, in any namespace, whose state is not Resolved or Failed (Issues of remote clusters are not counted)

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

Federation status

apiVersion
string
Example:

"v1"

kind
string
Example:

"FederationStatus"

spec
object