argocd

Best Practices

• Use the app-of-apps pattern for managing multiple applications
• Enable automated sync with self-heal and prune for GitOps workflows
• Configure sync waves (argocd.argoproj.io/sync-wave annotation) for ordering
• Set ignoreDifferences for fields managed by controllers (e.g., replicas with HPA)
• Use server-side apply for large manifests (ServerSideApply=true)
• Configure retry strategy with backoff for transient failures
• Add resource health checks with custom health.lua scripts when needed
• Use AppProject to restrict source repos and destination clusters/namespaces
• Set finalizers for cascade deletion (resources.finalizer.argocd.argoproj.io)
• Use targetRevision with specific branches or tags, not HEAD in production
• Configure notification triggers for sync status changes
• Separate ArgoCD app definitions from application manifests in the repo

Documentation Sources