Environment Deployment Flow
A merge to develop publishes a develop image. Image Updater selects it and Argo CD deploys the relevant service to the Dev cluster. Teams run smoke and integration checks against the shared composition.
The release branch publishes release images. Test tracks only the active release stream. QA owns regression status; application teams own defect analysis and fixes.
Main or final tags publish production-eligible images. Production updates require release approval even when synchronization is automated. Sync windows and Argo CD project restrictions prevent accidental cross-environment deployment.
Health
Section titled “Health”A successful image push is not a successful deployment. Argo CD must report synchronized and healthy, Kubernetes rollout must complete, and required post-deployment checks must pass.