Getting Argo CD into your pipeline is where it starts paying off - automated, repeatable and reviewed. Here is a working integration and the habits that keep it reliable.
A working pipeline snippet
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 pushDo this
- 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
Avoid this
- 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.