These tutorials walk through setting up Istio multi-cluster meshes on OpenShift using Red Hat Advanced Cluster Management (ACM) 2.17+, the Cluster Observability Operator (COO), and Kiali. ACM provides fleet management, and its multicluster observability add-on (MCOA) federates Istio and container metrics from each spoke cluster to hub Thanos via ScrapeConfig and PrometheusRule objects (requires COO on hub and spokes). COO also provides Perses metrics dashboards and the distributed tracing console plugin for Tempo, both integrated into the OpenShift console.

The finished environment has three OpenShift clusters: an ACM hub (ossm-kiali-hub) for fleet management and central Thanos metrics, and two Istio primary spokes (ossm-kiali-spoke and ossm-kiali-spoke-two) that share one multi-primary mesh. Kiali runs on the first spoke and reaches the second via a multi-cluster secret; Perses and Tempo add multi-cluster dashboards and tracing; health-status alerts can fire on each cluster or on the hub, and optionally appear on NetObserv Network Health. Click the diagram to open a full-size SVG in a new tab.

Finished multi-cluster environment

Badges such as G2:P5 mean Guide 2, Phase 5. Read Guides 1 → 2 → 3 in order; each guide page includes a progressive diagram of the environment as it exists when that guide finishes. Guide 4 (health status alerts and optional NetObserv Network Health) can also be followed standalone on any OpenShift cluster with Kiali.

Start with the hub/spoke guide; the multi-primary and dashboards/tracing guides build on it in sequence. Finish up with the health status alerts guide.