Security with Argo CD is mostly correct, boring defaults applied consistently. Here is the short list that removes most of the risk.
Safe defaults
- Scope Argo CD RBAC per project and team
- Encrypt secrets (SOPS/Sealed Secrets) rather than committing plaintext
Wire it into the pipeline
CI only updates the image tag in Git; Argo CD does the deploy.
bump-image:
script:
- yq -i '.image.tag = strenv(CI_COMMIT_SHA)' apps/web/values.yaml
- git commit -am "web $CI_COMMIT_SHA" && git pushReinforcing habits
- 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.