Most Argo CD pain is self-inflicted and predictable. Here are the mistakes we see most, and the fix for each.
Mistake 1: Letting people kubectl apply straight to the cluster, causing endless drift
Fix: Adopt app-of-apps to manage many Applications declaratively. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 2: Auto-sync without prune, leaving orphaned resources behind
Fix: Enable selfHeal + prune so the cluster always matches Git. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
Mistake 3: Storing plaintext secrets in the Git repo
Fix: Use Sealed Secrets/SOPS so secrets can live safely in Git. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.
A safer baseline
An Application that tracks a Git path and self-heals.
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata: { name: web, namespace: argocd }
spec:
project: default
source:
repoURL: https://github.com/acme/deploy.git
targetRevision: main
path: apps/web
destination:
server: https://kubernetes.default.svc
namespace: web
syncPolicy:
automated: { prune: true, selfHeal: true }
syncOptions: [CreateNamespace=true]Want senior help putting Argo CD to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.