Back to results for “RBAC”
ArgoCD › GitOps Principles

What are common anti-patterns in GitOps?

Advanced

Answer

Anti-patterns include: manual kubectl changes bypassing Git, plaintext secrets in Git, mixing app code and config confusingly, giving CI direct cluster credentials (push), not pinning revisions in prod, and huge blast-radius roots. Each undermines the source-of-truth, security, or reproducibility goals of GitOps.
Real-world example A team eliminates ad-hoc kubectl edits by enabling selfHeal so all changes must go through Git.

Common follow-ups: Why avoid manual kubectl edits? | What's wrong with CI holding cluster creds?