Open Akshaya-T opened 1 year ago
@jannfis the image updater was working for the strategies we defined, but suddenly the build pipeline pushed images with older incorrect timestamps (Jan 1, 1970 in GCR), from then image updater started failing and reverting the images.
Actually this is not a bug. It is mentioned in the ArgoCD Image Updater documentation here: https://argocd-image-updater.readthedocs.io/en/stable/basics/update-strategies/#latest-update-to-the-most-recently-built-image
Fluxcd can update a reproducible build by sorting part of an image tag using regex: https://fluxcd.io/flux/components/image/imagepolicies/#examples. Maybe we can implement something like this in ArgoCD Image Updater? This would be very useful
Describe the bug Images getting pushed to the GCR using docker-build-push action in Github. But when image updater tries to update the latest tag in the deployment it errors out.
Expected behavior Image updater should update the latest tag in the pods.
Additional context Images are getting created with the timestamp Jan 1, 1970 in GCR. For those images I could face the issue.
Version
Logs