ArgoCD - what need be done after build a new image

[harshada2828]

Setup:

• My application code and Helm charts are in the same Git repository.
• Cloud Build is configured to build and push Docker images to Google Artifact Registry after every code update. I use ArgoCD to point to the Helm chart repository and deploy my application on a GKE cluster.

Current Progress:

• I have successfully deployed my application via ArgoCD, and it is accessible through its Ingress URL. The application currently uses Docker images with the latest tag.

Challenge:

• When developers update the code, Cloud Build automatically triggers, builds, and pushes the new image to the Artifact Registry (still tagged as latest).
  
  
  

  Question:

  • What steps should I configure in ArgoCD to detect these changes and trigger a redeployment?
  • How can ArgoCD know that the image (tagged as latest) has changed and ensure that the updated image is pulled and deployed?

  Looking for the best practices to handle this scenario efficiently. Thank you!

[grsiepka]

From a best practice perspective, I would move away from using "latest" tag on your container images.  Use proper versioning, and update your k8s deployment manifest to look for versioned image.  By updating a version tag in your helm chart / manifest, ArgoCD should notice that change and deploy your new version.