Managing Application Dependencies in Argo CD
summary
Argues that Argo CD treats an Application CRD as the atomic deployable, then gives three concrete dependency patterns: eventual consistency (use probes, health checks, and the annotation skip-dry-run-on-missing-resource to retry until dependent CRs appear), app-of-apps (use sync waves inside a parent Application to order bootstrapping), and Progressive syncs (alpha) via ApplicationSet (creates all Applications but disables autosync and rolls them in label-ordered batches). Emphasizes enabling application resource health checks and readiness/liveness probes for these patterns to work.
AI-written summary · about
chapters (10)
- 0:00Managing dependencies in Argo CD
- 3:29Argo CD app lifecycle
- 6:40Three dependency patterns
- 7:23Prerequisites for dependency patterns
- 10:15Eventual consistency solution
- 12:44App of apps pattern
- 15:11Application sets & progressive syncs
- 18:25Best practices for app health
- 20:32Depends-on workflow request
- 21:16Q&A on DAG workflows
related talks
36mMulti-cluster, multi-apps, multi-value deployments using Argo CD Application Sets
25mExtending Argo CD with Health Checks and Resource Actions
42mLet's Learn About ArgoCD
23mArgo at Scale: Navigating Complex Multi-Dimensional Deployments Across H...
25mExtending Argo Projects: Customizing Argo CD and Argo Rollouts...
28mCross-Cluster Progressive Delivery: Rolling Out Apps With Arg...
28mThe ArgoCD AppProject - What Is a Project and How to Power Your...
18mUnveil the Secret Ingredients for Argo CD in the Enterprise-Scale