Multi-Cluster GitOps Application Delivery Using ArgoCD and OCM Hub-Spoke Pull Model Pattern
summary
Integration of Argo CD with OCM implements a pull hub-spoke model by creating a propagation controller that wraps Argo CD Application templates into ManifestWork objects so per-cluster Argo CD instances pull and apply manifests locally. Status collection uses OCM Search + a resource-sync and aggregation controller to emit a MultiClusterApplicationSetReport. Tested with 20 ApplicationSets across 500 managed clusters (~10k Applications) to prove scalability versus push limits (~1k apps or >100 clusters). Known gaps: manifestwork feedback rules and incomplete failed-resource reporting; many prerequisites.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:10What is OCM
- 1:46Placement Decision
- 3:06Pro Model
- 5:39Pro Model Details
- 12:40Component Overview
- 18:04Prerequisites
- 20:38Demonstration
- 28:00Limitations
- 31:53Questions
related talks
21mApplied GitOps with Argo CD Autopilot Using Multiple Clusters with an ApplicationSet
34mInfrastructure at Scale Using ArgoCD
24mScaling GitOps Using ArgoCD Application-Sets: Lesson Learnt
01h 38mScaling Multi-cluster Management with Argo CD and Application Sets
35mManage More Clusters with Less Hassle, with Argo CD Application Sets
36mMulti-cluster, multi-apps, multi-value deployments using Argo CD Application Sets
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
10mKeynote Scaling GitOps Using ArgoCD Application Sets Lesson Learnt