Argo CD reconciles GitOps configuration changes into Kubernetes. In a promotion workflow, it takes over after the promotion process commits the desired changes to Git. section 3.5 section 3.5
The handoff separates promotion from deployment:
- Kargo discovers an image and writes its updated tag to the GitOps repository. section 3.5
- Argo CD detects the changed commit, syncs the application, and lets the cluster converge on the promoted version. section 3.5
Promoting demo-app
After the dev overlay changes from image 1.0.0 to 1.1.0, Argo CD syncs the demo-dev Application; the namespace then runs the promoted image. section 3.5
Figure 3.3 End-to-end promotion of the demo-app image, from the container registry to a running pod in the demo-dev namespace. The six lettered steps, A through F, mark the boundary between layers. Kargo owns steps A through D; Argo CD owns steps E and F. The Warehouse and Stage are Kargo resources living in the cluster; the GitOps repository and the Argo CD Application are infrastructure Kargo writes to but does not own. The Freight object is the lineage record that ties the whole chain together.
Follow the six-step flow from image discovery to a running pod, with the boundary between Kargo’s Git write and Argo CD’s reconciliation made explicit. section 3.5

