Argo CD rewards a little discipline. These are the practices that keep it maintainable as a team and a codebase grow.
The practices
- 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
What good looks like
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]Anti-patterns to retire
- 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
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.