When Argo CD misbehaves, the cause is usually one of a handful of familiar issues. Here is how to spot and fix them fast.
The usual suspects
- Letting people kubectl apply straight to the cluster, causing endless drift
- Auto-sync without prune, leaving orphaned resources behind
- Storing plaintext secrets in the Git repo
Commands for diagnosis
argocd app sync web
argocd app get web
argocd app history web
argocd app rollback web 3Prevent the repeat
- Adopt app-of-apps to manage many Applications declaratively
- Enable selfHeal + prune so the cluster always matches Git
- Use Sealed Secrets/SOPS so secrets can live safely in Git
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.