Question

Your platform team uses Argo CD to manage 40 microservices across several environments. Each service currently has its own Argo CD Application manifest, but onboarding a new environment means manually creating dozens of Application objects. You want a single, version-controlled entry point in Git from which Argo CD automatically discovers and manages all the individual Application resources. Which GitOps approach best achieves this?

Accepted Answer

Use the App-of-Apps pattern: create one root Argo CD Application that points to a Git directory containing the child Application manifests.

Answer

Manually run 'kubectl apply' for each Application manifest whenever a new environment is added, then let Argo CD sync.

Answer

Combine all 40 services into a single Helm chart and deploy it as one Argo CD Application to reduce the object count.

Answer

Switch to a push-based CI pipeline that runs 'argocd app create' commands for each service on every commit.