Add Hybrid Mesh Platform sandbox pattern#686
Conversation
|
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. |
|
Hi @mbaldessari and team, I have opened this Pull Request to propose adding the Hybrid Mesh Platform architecture blueprint to the Validated Patterns documentation. This architecture provides a GitOps-first, hub-spoke reference design to scale fleet governance across multiple OpenShift clusters. The stack is validated using an Industrial Edge factory IoT scenario as the proof workload. Key highlights of the platform architecture include:
The underlying repository and full implementation details can be found at: github.com/maximilianoPizarro/platform-hub-spoke-config. I would highly appreciate your review, feedback, or any guidance on required adjustments to ensure this aligns perfectly with the Validated Patterns standards. Thank you for your time and support! |
Introduces hub-spoke multi-cluster GitOps docs with architecture diagrams, getting started, observability, and Industrial Edge extension pages. Co-authored-by: Cursor <cursoragent@cursor.com>
Align depth with the platform-hub-spoke-config site: journey intro, end-to-end flows, Skupper listeners, gateway circuit breaking, and expanded observability and scaffolding guidance. Co-authored-by: Cursor <cursoragent@cursor.com>
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>
Add architecture narrative for fleet management and Central/SecuredCluster topology, ACS-2 console image, and expanded getting-started operator guidance. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
… 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>
b127450 to
e06261d
Compare
|
Hi @mbaldessari, thanks for looking at this PR. Here's a summary of what changed since the initial submission: Updates in this force-push (rebased on latest
The pattern documentation does not include the Let me know if you need any adjustments! |
- 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>
|
Hi @mbaldessari, updated the PR with a fresh rebase on Changes in this update:
No NeuroFace content included. All tested on AWS with OpenShift 4.20 (hub + 2 spokes). Ready for review when you have time! |
Add workshop-style hero images (white background, Red Hat branding) as primary visuals for landing, architecture, observability, scaffolding, hub-gateway, industrial-edge, and getting-started pages. Previous console screenshots retained as supplementary detail views. Signed-off-by: Maximiliano Pizarro <maximiliano.pizarro.5@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Expand the pattern overview with hub-spoke architecture summary, service mesh traffic flow, OpenShift AI MaaS, Kuadrant API gateway, and detailed workshop dual-track description aligned with the Hybrid Mesh AI Showroom content. Signed-off-by: Maximiliano Pizarro <maximiliano.pizarro.5@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Separate hero images with tables, bullet explanations, and flow descriptions so content doesn't appear as stacked screenshots without context. Signed-off-by: Maximiliano Pizarro <maximiliano.pizarro.5@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Every image now has an italic caption below explaining what the screenshot shows, preventing wall-of-images without context. Signed-off-by: Maximiliano Pizarro <maximiliano.pizarro.5@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Add explanatory paragraphs between every screenshot: cross-cluster metrics flow, per-dashboard descriptions, Kiali topology detail, and Kafka Console multi-cluster explanation. Signed-off-by: Maximiliano Pizarro <maximiliano.pizarro.5@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
Hi! I am a bit confused here, from a quick look at the actual repo, it seems to use non of the validated patterns pieces (pattern-operator, secrets loading, clustergroup chart, other charts, etc). https://validatedpatterns.io/contribute/implementation/ here we have a bit of guidance, but it's really best to start off an existing pattern and expand that (multicloud-gitops is usually the recommended one). |
|
Hi @mbaldessari — thank you for the feedback, and sorry for the confusion. You're absolutely right: platform-hub-spoke-config is a standalone App-of-Apps implementation and does not use the Validated Patterns framework (no clustergroup chart, pattern-operator, VP secrets loading, or the standard chart layout). This docs PR was ahead of the implementation shape VP expects. What I'll do next: Fork multicloud-gitops as the base and migrate our Hybrid Mesh Platform capabilities (Industrial Edge on spokes, ambient Service Mesh, Service Interconnect/Skupper, Connectivity Link/RHCL, observability, ACS, OpenShift AI, etc.) onto the VP structure — starting from the recommended pattern rather than documenting a parallel layout. Thanks again for pointing me to the right starting point — much appreciated. |
|
Superseded by a new PR with VP-conformant implementation:
The legacy App-of-Apps repo (platform-hub-spoke-config) remains frozen for live workshop deployments until cutover is validated on demo.redhat.com. |
Summary
sandbox-tier pattern undercontent/patterns/hybrid-mesh-platform/.static/images/hybrid-mesh-platform/and spellcheck entries in.wordlist.txt.Contributor: Maximiliano Pizarro (Specialist Solution Architect at Red Hat)
Pattern repo: https://github.com/maximilianopizarro/platform-hub-spoke-config
Pages added
_index.mdgetting-started.mdarchitecture.mdhub-gateway.mdobservability.mdindustrial-edge.mdscaffolding.mdideas-for-customization.mdTest plan
.wordlist.txtupdated)make buildin container)/patterns/hybrid-mesh-platform//images/hybrid-mesh-platform/Made with Cursor