Update Hybrid Mesh Platform: cluster sizing, AWS 4.20 tags, Kairos AI ops.

- Add tested_on metadata: AWS, OpenShift 4.20, 3-cluster topology
- Add cluster sizing table (hub 24vCPU/96GiB, spokes 12vCPU/48GiB)
- Reference current release ocp-420-v5
- Add AI-assisted operations (Kairos) section with 5 screenshots
- Rebase on upstream/main for clean merge

Signed-off-by: Maximiliano Pizarro <maximiliano.pizarro.5@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

Author: maximilianoPizarro

.wordlist.txt

@@ -514,6 +514,7 @@ kafdrop
 kafkasource
 kafkatopic
 kafkatopics
+kairos
 kam
 kamelet
 kaoto

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

@@ -25,6 +25,10 @@ links:
   install: getting-started
   bugs: https://github.com/maximilianopizarro/platform-hub-spoke-config/issues
   feedback: https://docs.google.com/forms/d/e/1FAIpQLScI76b6tD1WyPu2-d_9CCVDr3Fu5jYERthqLKJDUGwqBg7Vcg/viewform
+tested_on:
+  platform: AWS
+  ocp_version: "4.20"
+  topology: "3 clusters (hub + east spoke + west spoke)"
 contributor:
   name: Maximiliano Pizarro
   contact: mailto:maximilianopizarro5@gmail.com
@@ -39,7 +43,9 @@ contributor:
 
 **Hybrid Mesh Platform** is a multi-cluster GitOps platform using Red Hat products. It implements a hub-spoke topology that centralizes governance with Red Hat Advanced Cluster Management (ACM), delivers [Industrial Edge](/patterns/industrial-edge/) workloads on regional spokes, uses OpenShift Service Mesh in ambient mode for east-west connectivity, layers Connectivity Link (Kuadrant) for API-aware ingress policy, exposes Grafana dashboards for cross-cluster visibility, and integrates Advanced Cluster Security (ACS) for vulnerability and runtime protection.
 
-**Supported on:** Red Hat OpenShift Container Platform 4.20 (4.14 or newer per cluster).
+**Tested on:** Red Hat OpenShift Container Platform **4.20** on **AWS** (hub + east spoke + west spoke, multinode 3 workers each). Compatible with 4.14+ per cluster.
+
+**Current release:** [ocp-420-v5](https://github.com/maximilianoPizarro/platform-hub-spoke-config/releases/tag/ocp-420-v5) — Camel Dashboard on east/west spokes, Skupper token sync, Kafka Console broker DNS fixes.
 
 Read **concept → mechanics → operations**: start with [Architecture](architecture), install via [Getting Started](getting-started), scaffold workloads via [Scaffolding](scaffolding), then use platform chapters (**Hub Gateway**, **Observability**, **Industrial Edge**) before drilling into the [pattern repository](https://github.com/maximilianopizarro/platform-hub-spoke-config).
 

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

@@ -79,6 +79,22 @@ Use cluster names **`hub`**, **`east`**, and **`west`**. Namespace **`stackrox`*
 1. Access to public container registries (or mirrored equivalents)
 2. Access to your Git repository (fork of `platform-hub-spoke-config`)
 
+### Cluster sizing (AWS — OpenShift 4.20)
+
+Tested on **demo.redhat.com** with the following provisioning parameters:
+
+| Cluster | Workers | vCPU/worker | Memory/worker | Total capacity |
+| --- | --- | --- | --- | --- |
+| **Hub** | 3 | 8 | 32 GiB | 24 vCPU / 96 GiB |
+| **East spoke** | 3 | 4 | 16 GiB | 12 vCPU / 48 GiB |
+| **West spoke** | 3 | 4 | 16 GiB | 12 vCPU / 48 GiB |
+
+Hub estimated workload: ~12.5 CPU / ~29 GiB (ACM, ACS Central, Developer Hub, data lake Kafka 3-replica, Service Mesh, OpenShift AI, hub gateway).
+
+Spoke estimated workload: ~5.5 CPU / ~11 GiB (Industrial Edge, factory Kafka, ACS SecuredCluster, Service Mesh ambient).
+
+For constrained environments, use `values-lite.yaml` on the hub to disable heavy components (OpenShift AI, ACS, Grafana dashboards, hub gateway).
+
 ## Repository layout
 
 ```

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

@@ -189,6 +189,20 @@ Re-sync `kafka-console` after Skupper listeners are healthy. Confirm `listNodes`
 | `multi-cluster-istio` | Hub | Hub, Prometheus-East, Prometheus-West |
 | `local-metrics` | Each spoke | Local Prometheus (UWM/Thanos) |
 
+## AI-assisted operations (Kairos)
+
+The platform integrates AI-driven operational intelligence through event correlation, anomaly detection, and human-in-the-loop workflows:
+
+[![Kairos — event correlation and alerting](/images/hybrid-mesh-platform/kairos-events.png)](/images/hybrid-mesh-platform/kairos-events.png)
+
+[![Kairos — historical analysis and trends](/images/hybrid-mesh-platform/kairos-history.png)](/images/hybrid-mesh-platform/kairos-history.png)
+
+[![Kairos — human-in-the-loop decision workflows](/images/hybrid-mesh-platform/kairos-human-in-the-loop.png)](/images/hybrid-mesh-platform/kairos-human-in-the-loop.png)
+
+[![Kairos — AI agents for autonomous remediation](/images/hybrid-mesh-platform/kairos-ia-agents.png)](/images/hybrid-mesh-platform/kairos-ia-agents.png)
+
+[![Kairos — observability-driven insights](/images/hybrid-mesh-platform/kairos-observability.png)](/images/hybrid-mesh-platform/kairos-observability.png)
+
 ## References
 
 - [OpenShift Observability](https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/monitoring/)