A successful build doesn't mean your new version is live.
Suppose Git requests v2 , while the live Kubernetes Deployment still references v1 . The new image might already be in the registry, but the cluster configuration has not caught up.
This is a useful way to understand Argo CD: follow one configuration change from Git to the cluster, then check what that change actually achieved.
The example below is illustrative. The image names are placeholders, and the diff is not a complete Kubernetes manifest.
Separate the responsibilities
For this container-based example, the delivery workflow has three distinct parts:
Responsibility What happens
CI Test the application, build a container image and publish it to a registry.
Git Store the deployment configuration that references the intended image version.
Argo CD Compare desired configuration with live resources and synchronize changes.
Kubernetes controllers then carry out the rollout after the resource configuration changes.…