Add Connectivity Link and console topology images to docs.

Download missing diagrams (connectivity-link hub/spoke, Skupper
console views, Grafana/Kiali/Kafka panels) and embed them in
architecture, hub-gateway, observability, and getting-started pages.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: maximilianoPizarro

content/patterns/hybrid-mesh-platform/_index.md

@@ -69,7 +69,7 @@ Architecture diagrams in this documentation illustrate Git, ACM, Skupper VAN, an
 | --- | --- |
 | Architecture deep dive | [Architecture](architecture) |
 | Install flow | [Getting Started](getting-started) |
-| Hub Gateway | [Hub Gateway](hub-gateway) |
+| Hub Gateway and Connectivity Link | [Hub Gateway](hub-gateway) |
 | Observability | [Observability](observability) |
 | Industrial Edge (multi-cluster) | [Industrial Edge](industrial-edge) |
 | Scaffolding | [Scaffolding](scaffolding) |

content/patterns/hybrid-mesh-platform/architecture.md

@@ -123,6 +123,18 @@ Red Hat Service Interconnect creates a **Virtual Application Network (VAN)** tha
 
 [![Service Interconnect console topology](/images/hybrid-mesh-platform/service-interconnect-console-topology.png)](/images/hybrid-mesh-platform/service-interconnect-console-topology.png)
 
+### Skupper Network Observer (console views)
+
+The Skupper Network Observer visualizes the Virtual Application Network — sites, listeners, connectors, and process-level traffic across hub, east, and west:
+
+[![Skupper Network Observer — sites and links](/images/hybrid-mesh-platform/service-interconnect-console.png)](/images/hybrid-mesh-platform/service-interconnect-console.png)
+
+[![Skupper console — components, listeners, and connectors](/images/hybrid-mesh-platform/service-interconnect-console-topology-process.png)](/images/hybrid-mesh-platform/service-interconnect-console-topology-process.png)
+
+[![Skupper console — process-level topology](/images/hybrid-mesh-platform/service-interconnect-console-process.png)](/images/hybrid-mesh-platform/service-interconnect-console-process.png)
+
+[![Skupper console — built-in metrics (TCP bytes, latency, connections)](/images/hybrid-mesh-platform/service-interconnect-console-metrics.png)](/images/hybrid-mesh-platform/service-interconnect-console-metrics.png)
+
 ### Hub listeners (namespace `service-interconnect`)
 
 | Listener | Port | Purpose |
@@ -156,6 +168,12 @@ Charts: `components/service-interconnect` (hub), `components/spoke-interconnect`
 
 Each spoke runs a Gateway API gateway (`components/spoke-gateway`) that fronts all Industrial Edge services. Skupper exposes **one** gateway per spoke instead of every microservice individually.
 
+[![Spoke gateway aggregation diagram](/images/hybrid-mesh-platform/arch-spoke-gateway.png)](/images/hybrid-mesh-platform/arch-spoke-gateway.png)
+
+[![Spoke Gateway API — Connectivity Link view](/images/hybrid-mesh-platform/connectivity-link-spoke-gateway.png)](/images/hybrid-mesh-platform/connectivity-link-spoke-gateway.png)
+
+Hub-side Gateway API and HTTPRoute policy topology: see [Hub Gateway — Connectivity Link topology](hub-gateway#connectivity-link-topology).
+
 ## Multi-cluster observability pipeline
 
 Spoke Thanos Querier is reached through nginx auth-proxy Connectors. Hub Listeners `prometheus-east` and `prometheus-west` become Grafana HTTP datasources (no bearer token from hub).

content/patterns/hybrid-mesh-platform/getting-started.md

@@ -25,6 +25,16 @@ After a successful hub deploy and spoke registration, expect:
 
 Then continue with [Scaffolding](scaffolding) to deploy a new edge instance on east or west.
 
+## Platform operators (reference)
+
+The hub chart deploys ACM, GitOps, ACS, and related operators before application workloads. Console views after sync:
+
+[![Advanced Cluster Management — fleet view](/images/hybrid-mesh-platform/ACM.png)](/images/hybrid-mesh-platform/ACM.png)
+
+[![OpenShift GitOps — Argo CD Applications](/images/hybrid-mesh-platform/product-argocd-openshift-gitops.png)](/images/hybrid-mesh-platform/product-argocd-openshift-gitops.png)
+
+[![Advanced Cluster Security — central console](/images/hybrid-mesh-platform/ACS.png)](/images/hybrid-mesh-platform/ACS.png)
+
 ## Prerequisites
 
 - Red Hat OpenShift Container Platform **4.20** (reference version; 4.14+ supported per cluster)

content/patterns/hybrid-mesh-platform/hub-gateway.md

@@ -8,11 +8,35 @@ aliases: /hybrid-mesh-platform/hub-gateway/
 
 The hub gateway provides centralized HTTP ingress on the hub cluster with behaviors similar to an F5 BIG-IP ADC: VIP-style routing, TLS termination at the edge, and weighted traffic splits across backend services or spoke-derived routes.
 
-Implementation chart: `components/hub-gateway`.
+Implementation chart: `components/hub-gateway`. Connectivity Link operator: `components/rhcl-operator`.
 
-[![Hub gateway](/images/hybrid-mesh-platform/connectivity-link-hub-gateway.png)](/images/hybrid-mesh-platform/connectivity-link-hub-gateway.png)
+## Connectivity Link topology
 
-[![Spoke gateway](/images/hybrid-mesh-platform/connectivity-link-spoke-gateway.png)](/images/hybrid-mesh-platform/connectivity-link-spoke-gateway.png)
+Connectivity Link (Kuadrant) brings multi-cluster ingress and policy using Kubernetes Gateway API — DNS, TLS, rate limiting, and auth patterns layered on `Gateway` and `HTTPRoute` resources. In this platform, Gateway API objects align with hub gateway routing (including weighted splits similar to hardware ADC behavior). Policies may be disabled initially; enable Kuadrant `AuthPolicy`, `RateLimitPolicy`, and DNS/TLS strategies as you harden environments.
+
+[![Gateway API policy topology — hub HTTPRoute and route rules](/images/hybrid-mesh-platform/connectivity-link-hub.png)](/images/hybrid-mesh-platform/connectivity-link-hub.png)
+
+_Gateway API policy topology — hub-gateway, HTTPRoute, and route rules in the OpenShift Console._
+
+### Hub cluster
+
+Hub cluster Gateway API resources and HTTPRoute attachment to `hub-gateway-system`:
+
+[![Hub cluster Gateway API and HTTPRoute](/images/hybrid-mesh-platform/connectivity-link-hub-gateway.png)](/images/hybrid-mesh-platform/connectivity-link-hub-gateway.png)
+
+### Spoke clusters
+
+Spoke cluster Gateway API and backend services exposed through the mesh:
+
+[![Spoke cluster Gateway API and backends](/images/hybrid-mesh-platform/connectivity-link-spoke.png)](/images/hybrid-mesh-platform/connectivity-link-spoke.png)
+
+Spoke gateway aggregating Industrial Edge services for cross-cluster exposure (single Skupper Connector target per spoke):
+
+[![Spoke gateway aggregating Industrial Edge services](/images/hybrid-mesh-platform/connectivity-link-spoke-gateway.png)](/images/hybrid-mesh-platform/connectivity-link-spoke-gateway.png)
+
+[![Spoke gateway architecture — Gateway API aggregation](/images/hybrid-mesh-platform/arch-spoke-gateway.png)](/images/hybrid-mesh-platform/arch-spoke-gateway.png)
+
+Verify Connectivity Link reconciliation by inspecting `Gateway` status conditions and `HTTPRoute` `spec.parentRefs` — not only Pod labels. Chart path: `components/rhcl-operator`.
 
 ## Gateway API theory
 
@@ -100,9 +124,9 @@ gateway:
 
 Set `enabled: false` to disable circuit breaking entirely.
 
-## Relationship to Connectivity Link
+## Relationship to Connectivity Link and Service Mesh
 
-Connectivity Link (Kuadrant) layers DNS automation, TLS policies, and advanced controls atop Gateway API. Start with plain HTTPRoutes for incremental adoption; enable Kuadrant policies when teams require DNS/TLS/rate-limit governance at scale.
+Connectivity Link layers DNS automation, TLS policies, and advanced controls atop the Gateway API topology shown above. Service Mesh ambient (ztunnel/waypoints) carries east-west traffic between gateway hops and workloads. Start with plain HTTPRoutes for incremental adoption; enable Kuadrant policies when teams require DNS/TLS/rate-limit governance at scale.
 
 ## IoT Dashboard integration
 

content/patterns/hybrid-mesh-platform/industrial-edge.md

@@ -48,6 +48,8 @@ Each spoke (east/west) runs the same stack independently — the hub aggregates
 | CI/CD | Tekton pipelines (buildah + deploy) | `industrial-edge-ci` |
 | Visualization | `line-dashboard` (WebSocket consumer) | `industrial-edge-tst-all` |
 
+[![OpenShift AI — KServe inference on spoke](/images/hybrid-mesh-platform/openshift-ia.png)](/images/hybrid-mesh-platform/openshift-ia.png)
+
 End-to-end on a spoke: sensor → MQTT → Camel K → Kafka → optional ML → dashboard; MirrorMaker streams toward centralized storage for model training (see [Architecture](architecture#follow-the-request--one-temperature-reading-end-to-end)).
 
 ## Camel K integrations

content/patterns/hybrid-mesh-platform/observability.md

@@ -18,6 +18,26 @@ Grafana panels, Kiali graphs, and Kafka Console views help you confirm that fact
 
 [![Observability pipeline](/images/hybrid-mesh-platform/arch-observability-pipeline.png)](/images/hybrid-mesh-platform/arch-observability-pipeline.png)
 
+## Grafana dashboard views
+
+Multi-cluster fleet dashboards on the hub (east/west traffic, Service Mesh L4/L7, Kafka health):
+
+[![Grafana — east-west traffic and Service Mesh](/images/hybrid-mesh-platform/product-grafana-observability-2.png)](/images/hybrid-mesh-platform/product-grafana-observability-2.png)
+
+[![Grafana — multi-cluster Istio metrics (ztunnel L4)](/images/hybrid-mesh-platform/product-grafana-observability-3.png)](/images/hybrid-mesh-platform/product-grafana-observability-3.png)
+
+[![Grafana — extended fleet KPI panels](/images/hybrid-mesh-platform/product-grafana-observability-4.png)](/images/hybrid-mesh-platform/product-grafana-observability-4.png)
+
+## Kiali and mesh topology views
+
+[![Kiali — service mesh traffic graph](/images/hybrid-mesh-platform/product-kiali-service-mesh-2.png)](/images/hybrid-mesh-platform/product-kiali-service-mesh-2.png)
+
+## Kafka Console views
+
+[![Kafka Console — multi-cluster clusters and topics](/images/hybrid-mesh-platform/product-kafka-console-amq-streams-2.png)](/images/hybrid-mesh-platform/product-kafka-console-amq-streams-2.png)
+
+[![Kafka Console — broker and topic detail over Skupper](/images/hybrid-mesh-platform/product-kafka-console-amq-streams-3.png)](/images/hybrid-mesh-platform/product-kafka-console-amq-streams-3.png)
+
 ## Observability architecture
 
 | Layer | Technology | Role |