Skip to main content
GET
Federation Correlations
Minimum role: viewer. Takes no parameters. Lists the Issues of this cluster that carry a cross-cluster correlation ID, one item per distinct ID. When the same signalType is active in 3 or more clusters, the federation controller’s CorrelateAcrossClusters writes platform.chatcli.io/cross-cluster-correlation (xcluster-<id>) and platform.chatcli.io/affected-clusters (the number of clusters) on every matching Issue and raises spec.severity to critical, marking the ones it raised with platform.chatcli.io/elevated-severity: "true". A group keeps one ID: a new matching Issue joins the ID an earlier Issue already carries.

Correlation Fields

A cascade that DetectCascade marked (cascade-detected, cascade-source-cluster, cascade-source-issue) appears here only when the Issue also carries a correlation ID.

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

Cross-cluster correlations

apiVersion
string
Example:

"v1"

kind
string
Example:

"FederationCorrelations"

metadata
object
items
object[]