Refresh images and narrative for Hybrid Mesh Platform PR.

- Re-download all images with updated Red Hat corporate style
- Add Red Hat logo, OpenShift Console, Kubecost, Mailpit, Kairos
  community logo assets
- Expand product list: Dev Spaces, Quay, Virtualization, Gitea,
  Kafka Console
- Add spoke sync-wave reference table in Architecture
- Add Hybrid Mesh AI Workshop reference in landing page
- Tested on AWS with OpenShift 4.20 (hub + east + west)

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

Author: maximilianoPizarro

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

@@ -94,6 +94,10 @@ Screenshots and architecture diagrams in the pattern repository support full-scr
 
 **Next →** [Architecture](architecture) — understand how Git, ACM, and Skupper wire the three clusters together.
 
+## Workshop
+
+A hands-on **Hybrid Mesh AI Workshop** (dual-track: executive strategy + hands-on lab) is available for this platform. It covers ACM fleet management, ambient mesh, Developer Hub scaffolding, OpenShift AI, Kuadrant API gateway, and FinOps — all on a live RHDP hub-spoke fleet. See the [workshop site](https://maximilianopizarro.github.io/platform-hub-spoke-config/workshop/) for agenda and registration.
+
 ## Red Hat products used
 
 - Red Hat OpenShift Container Platform
@@ -107,6 +111,11 @@ Screenshots and architecture diagrams in the pattern repository support full-scr
 - Red Hat build of Apache Camel / Camel K
 - Red Hat OpenShift Pipelines (Tekton)
 - Red Hat Developer Hub (Backstage)
+- Red Hat OpenShift Dev Spaces (Kaoto, Continue AI)
+- Red Hat OpenShift Virtualization (KubeVirt)
+- Red Hat Quay (container registry on hub)
 - Red Hat Service Interconnect (Skupper)
+- Streams for Apache Kafka Console (hub fleet UI)
+- Gitea (in-cluster Git for scaffolder repos)
 - Mailpit (SMTP testing for notifications)
 - Observability stack (Prometheus-compatible metrics, Grafana, OpenTelemetry, Kiali)

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

@@ -160,13 +160,28 @@ Components deploy in strict order via Argo CD sync waves. Lower waves complete b
 
 [![Sync wave ordering](/images/hybrid-mesh-platform/arch-sync-waves.png)](/images/hybrid-mesh-platform/arch-sync-waves.png)
 
-Sync waves prevent operators from racing workloads — mesh and namespaces land before Industrial Edge and gateways. Typical progression:
+Sync waves prevent operators from racing workloads — mesh and namespaces land before Industrial Edge and gateways.
+
+### Hub sync-wave progression
 
 1. Namespaces and RBAC
 2. Operator subscriptions (ACM, GitOps, Service Mesh, Skupper, and others)
 3. Platform services (Developer Hub, ACS, interconnect sites)
-4. Observability stack
-5. Industrial Edge and gateway workloads
+4. Observability stack (Grafana, Kiali, OpenTelemetry)
+5. Industrial Edge data lake and gateway workloads
+
+### Spoke sync-wave reference
+
+| Wave | What deploys | Why this order |
+| --- | --- | --- |
+| 1 | Namespaces (no ambient label yet) | Names must exist before operators and workloads |
+| 2 | OLM Subscriptions | CRDs and operators installed |
+| 3 | Service Mesh 3 (Istio + ztunnel + ambient labels) | Mesh dataplane before application pods |
+| 4 | Observability, ACS SecuredCluster | Scraping and security after mesh |
+| 5 | Industrial Edge (Kafka, sensors, dashboard) | Pods enroll in ambient with HBONE ready |
+| 6 | Spoke gateway + Skupper interconnect | Routing after backends exist |
+
+Hub ApplicationSet for spokes runs at hub wave 5 after ACM placement is healthy.
 
 ## Service Interconnect (Skupper) topology