argocd-advanced

ArgoCD Advanced

Routing entrypoint for advanced/automation-oriented ArgoCD operations. Each sub-area has its own deep reference, preserved verbatim from the pre-consolidation skills, under References/.

Scope routing

Decision tree

Need new cluster registered with ArgoCD?           -> cluster-bootstrapping
Need new service deployed to existing clusters?    -> application-install
Need to fan one app definition across N clusters?  -> applicationset
Need images to roll forward automatically?         -> image-updater

Gotchas

• ApplicationSet generators are ordered. With matrix/merge generators, the parent generator's result is the input to the child — get the order wrong and you get an empty parameter set with no error.
• Image Updater + git write-back requires a write credential. A read-only repo cred will silently leave images stuck on the original version. Check Image Updater pod logs for permission denied on push.
• Bootstrap cluster secrets must carry the labels your ApplicationSet generators select on. A cluster registered without the expected label key/value is invisible to existing ApplicationSets — and there is no error, just zero apps.
• application-install ships a your organization/ExampleApp-specific template. The Workflows assume the multi-repo layout. If you're not in that environment, treat it as a reference pattern, not a runnable recipe.
• CRD versions matter. ApplicationSet ships with ArgoCD 2.3+; certain generators (SCM, pull request) need 2.5+. Read References/applicationset.md Version Compatibility before adopting.