An image tag is a mutable label: the same tag can point to different image content over time. Kargo can select registry tags for a Warehouse, then record each discovered image as Freight identified by a content hash. During promotion, it can rewrite a GitOps configuration from one tag to another. section 3.5.5 section 3.5
Selecting and promoting a tag
A Warehouse can discover demo-app:1.1.0 when it satisfies the configured semver constraint. A dev promotion then changes the GitOps overlay from 1.0.0 to 1.1.0. A constraint of >=1.0.0 will not match tags such as latest, main, or v1.0.0-rc1. section 3.5 section 3.6.1
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.
Trace an image from registry discovery through tag rewrite and deployment, including the handoff from Kargo to Argo CD. section 3.5






