As platforms grow, application onboarding, add-ons, and environment drift become hard to reason about.
Case 13
Argo CD App of Apps
As platforms grow, application onboarding, add-ons, and environment drift become hard to reason about.
01
Evidence
Problem, constraints, architecture, result.
Bootstrap order, namespace ownership, secrets, cluster add-ons, team autonomy, and rollback visibility.
Argo CD app-of-apps pattern with platform add-ons, application sets, sync waves, health checks, and environment-level ownership.
Platform state becomes visible in Git and easier to bootstrap, audit, and recover.
02
Snapshot
Field notes.
- Problem
- As platforms grow, application onboarding, add-ons, and environment drift become hard to reason about.
- Constraints
- Bootstrap order, namespace ownership, secrets, cluster add-ons, team autonomy, and rollback visibility.
- Architecture
- Argo CD app-of-apps pattern with platform add-ons, application sets, sync waves, health checks, and environment-level ownership.
- Result
- Platform state becomes visible in Git and easier to bootstrap, audit, and recover.
03
Related
Nearby systems.
Cloud-Native AI Gateway
AI usage needs routing, policy, budget awareness, and provider resilience.
Result: AI becomes operable infrastructure, not an opaque API call.
Kanister Backup & Restore
Application-aware Kubernetes restores need more than volume snapshots and manual runbooks.
Result: Restore behavior becomes repeatable, reviewable, and easier to exercise before an incident.
GitOps: Argo CD & Flux
Teams need a clear delivery model before GitOps becomes another layer of operational confusion.
Result: GitOps decisions become explicit platform contracts instead of tool preference debates.
Available for meaningful infrastructure conversations