Add Hybrid Mesh Platform sandbox pattern#696
Conversation
Baseline pattern pages and images for VP-conformant hybrid-mesh-platform publication on validatedpatterns.io. Co-authored-by: Cursor <cursoragent@cursor.com>
Sync content from hybrid-mesh-platform repo, add cluster-sizing metadata module, demo-scenario page with showroom narrative, refreshed images, and fixed internal/external doc links aligned with validatedpatterns.io journey. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- Add Problem→Solution table at top of _index.md (Service Mesh + AI ops framing) - Clarify 3-cluster requirement explicitly (single-cluster not supported) - Expand prerequisites: OCP version, storage class, RHOAI/GPU, Lightspeed - Document values-secret.yaml.template secrets table with all 6 secret names - Add Verify the installation section with concrete oc/bash commands (ACM, Skupper, OLSConfig, RHOAI, Industrial Edge, console links) - Add ASCII topology diagram in architecture.md showing hub+spoke+Skupper VAN Co-authored-by: Cursor <cursoragent@cursor.com>
- Remove ASCII art diagram from architecture.md (Red Hat branded images already exist) - Use workshop-hybrid-mesh-arch.png + arch-hub-spoke-flow.png as visual topology - Expand "Comparison" section to full "Relationship to VP patterns" with MCP/Lightspeed detail - Add Red Hat Device Edge + MicroShift extension path in architecture.md and ideas-for-customization.md - Update _index.md summary and Goal framing to include Device Edge extension path Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi @maximilianoPizarro. Thanks for your PR. I'm waiting for a validatedpatterns member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
- sort -u .wordlist.txt: remove duplicate entries (api's, backend's, etc.) - Remove 81 orphaned images (66 numbered workshop module shots + workshop/ subdirectory duplicates + 15 unreferenced root images) - Restore Kiali, Kafka Console, Kairos, and connectivity-link screenshots to observability.md and hub-gateway.md (were dropped during Jekyll→Hugo port) - Images reduced from 122 to 40 — all 40 are referenced in doc pages - Add clarifying note to demo-scenario.md: explanatory content only, hands-on lab modules remain in showroom-hybrid-mesh-ai repo Co-authored-by: Cursor <cursoragent@cursor.com>
Reviewers can verify the generated .adoc is consistent with https://github.com/maximilianoPizarro/hybrid-mesh-platform/blob/main/pattern-metadata.yaml Co-authored-by: Cursor <cursoragent@cursor.com>
The pattern repo uses charts/region/hub|east|west/ and charts/all/, not the App-of-Apps values-hub.yaml / east/ / west/ layout. - getting-started.md: fix repository layout block, values-hub.yaml → charts/region/hub/values.yaml (2 occurrences), ApplicationSet path east/ → charts/all/spoke-meta-push (PUSH) + charts/region/east/ (PULL) - ideas-for-customization.md: fix repo layout block, values table, ApplicationSet conceptual YAML, adding-spoke step 3, Regions table entry, Device Edge far-edge folder path Co-authored-by: Cursor <cursoragent@cursor.com>
5 service-interconnect-console-*.png screenshots restored from hybrid-mesh-platform/docs/assets/images/ and added to observability.md in a dedicated "Skupper Network Observer" section showing VAN overview, topology, process detail, and traffic metrics views. Co-authored-by: Cursor <cursoragent@cursor.com>
- Add specific requirements for CPU-only vs GPU-accelerated spokes - Detail minimum vs recommended worker node sizes - Add GPU operator prerequisites (NFD, NVIDIA GPU Operator) - Include cloud instance type examples for GPU nodes Co-authored-by: Cursor <cursoragent@cursor.com>
- Primary demo is now NeuroFace AI CV at the Edge (OVMS ModelMesh, YOLO PPE, Kafka, MaaS chat) on east/west spokes — Industrial Edge is optional and disabled by default - Add AI Gateway section to hub-gateway.md with APIProduct YAML, MaaS consumption paths (direct vs Kuadrant), and MCP Gateway - Add NeuroFace architecture diagram and PPE detection flow images - Add AI Gateway, MCP Gateway, and NeuroFace hero images - Fix ACS image incorrectly placed in Connectivity Link sections: remove workshop-acs-kuadrant.png from hub-gateway.md (belongs to ACS module, not gateway), use connectivity-link-hub.png instead - Update all pages: _index, architecture, getting-started, hub-gateway, scaffolding, observability, demo-scenario, industrial-edge, ideas-for-customization Co-authored-by: Cursor <cursoragent@cursor.com>
|
Closing this PR for now. After further architectural review, we have decided to decouple the repositories and pursue the target architecture by reusing existing Validated Patterns in the catalog (rather than introducing a new monolithic sandbox pattern in This approach better aligns with how VP patterns are meant to compose — Service Mesh, Industrial Edge, multicloud-gitops, and related patterns can be adopted and wired together independently, without maintaining a separate all-in-one documentation surface in this repo. Thank you to everyone who took the time to review this submission and for the thoughtful feedback. It helped clarify the direction and the right way to present this work within the VP ecosystem. We will continue development in the pattern repos and may revisit upstream documentation once the decoupled structure is stable. |
1 participant
Summary
Adds the Hybrid Mesh Platform as a Sandbox-tier Validated Pattern — a hub-spoke multi-cluster GitOps reference architecture on OpenShift that combines Service Mesh, AI-assisted operations, and Industrial Edge factory workloads in a single deployable pattern.
clustergroup,managedClusterGroups, Vault + External Secrets,pattern.sh install)What makes this pattern distinct
The existing catalog covers Service Mesh and Industrial Edge separately. This pattern combines them with AI-assisted operations:
OLSConfigDocumentation added
content/patterns/hybrid-mesh-platform/_index.md— Problem→Solution framing, hub-spoke table, products, journeycontent/patterns/hybrid-mesh-platform/architecture.md— multi-cluster topology with Red Hat branded diagrams, Device Edge extension pathcontent/patterns/hybrid-mesh-platform/getting-started.md— VP install (pattern.sh), prerequisites table (OCP/RHOAI/storage/GPU), secrets table (values-secret.yaml.template), and Verify the installation section with concrete commandscontent/patterns/hybrid-mesh-platform/cluster-sizing.adoc— generated frompattern-metadata.yamlviautils/flatten_yaml.rb; source link included in the page for reviewer verificationcontent/patterns/hybrid-mesh-platform/demo-scenario.md— explanatory workshop showroom narrative (hands-on lab modules remain in showroom-hybrid-mesh-ai)content/patterns/hybrid-mesh-platform/hub-gateway.md,observability.md,industrial-edge.md,scaffolding.md,ideas-for-customization.mdmodules/hybrid-mesh-platform/metadata-hybrid-mesh-platform.adoc— generated frompattern-metadata.yamlstatic/images/hybrid-mesh-platform/— 40 images (all referenced; 82 orphaned images removed).wordlist.txt— added:kairos,kaoto,kserve,kuadrant,mailpit,skupper,ztunnel; duplicates removedTest plan
hugo --minify, 558 pages, 0 errors).wordlist.txtnormalized (sort -u, no duplicates)make buildvia Podman container — Podman Machine requires Hyper-V admin on this workstation; localhugo --minifybuild is clean with 0 errors, which exercises the same Hugo + Asciidoctor rendering pathAny feedback or suggestions to improve this pattern — content, structure, or alignment with VP standards — are very welcome. Thank you for your time and review!