No dedicated repository, and gitops-duel does not implement an app-of-apps tree. This page documents the bootstrap pattern; measured Argo CD and Flux reconcile behaviour on kind lives in the GitOps duel.
Case 14 · Pattern
Argo CD App of Apps
Bootstrap as a tree: a root Application owns the forest, sync waves order growth, and recovery starts from structure — not a pile of apps.
00
Evidence home
Pattern case — proof lives next door.
01
How it works
Grow the forest from a root Application.
Argo CD App of Apps by Andrey Lesnikov — structural bootstrap so platforms recover by restoring the tree, not hunting orphans.
-
01
Plant the root
One Application declares the forest — bootstrap is structural from day one.
-
02
Branch by concern
Platform and environment apps hang from the root with clear ownership boundaries.
-
03
Wave the sync
Sync waves order growth so dependencies land before dependents pretend they can start.
-
04
Recover the trunk
When disaster hits, restore the root and the tree can grow again — auditable structure beats tribal memory.
02
Evidence
From problem to proof.
How the system is framed, operated, and proven — not a slide deck summary.
01
Argo CD apps proliferate without a root ownership model — sync windows and drift become noise.
02
You need multi-region promotion semantics or causal rehearsal before deploy — see Multi-Region GitOps and Architecture Rehearsal.
03
GitOps: Argo CD & Flux is the ownership spine. Policy as Code Guardrails gates what App-of-Apps is allowed to sync.
Constraints
Bootstrap order, namespace ownership, secrets, cluster add-ons, team autonomy, and rollback visibility.
03
Related
Nearby systems.
GitOps: Argo CD & Flux
Teams need a clear delivery model before GitOps becomes another layer of operational confusion
Delivery as explicit platform contracts
Multi-Region GitOps
Multi-region systems need repeatable promotion and rollback without turning every deployment into manual coordination
Regional drift stays auditable
Policy as Code Guardrails
Security and platform rules are often discovered only after deployment or during reviews
Standards enforced in CI, not slides
Available for meaningful infrastructure conversations