Jann Fischer

If I understand you correctly, then this is expected behavior: * You use update strategy `latest`, which specifies to update to the image that has been most recently built *...

I see some contrary information above. You say: > int-1635498622500 (this tag is the oldest in this repo) and later > argocd image updater only uses/consideres int-5 and not the...

OK, if `int-1635498622500` is newer than `int-5`, then probably there's something odd. Are you able to increase log level to `trace` and submit the logs? I have tried to reproduce...

Fix in #253 (released in v0.10.3) should have fixed that

You can set a renamed Kustomize image using the annotation `argocd-image-updater.argoproj.io/.kustomize.image_name` (refer to https://argocd-image-updater.readthedocs.io/en/stable/configuration/images/#custom-images-with-kustomize). This works fine with the app source method, and should also work when writing Kustomization files.

> Wouldn't it be better to use [...].image-name instead of [...].image_name? thinking Using - everywhere, but _ for the image name feels inconsistent. I think it actually is `image-name`, and...

There's some ongoing discussion in https://github.com/argoproj/argo-cd/pull/4084

Thanks a lot for some great suggestions and writing down your requirements, @hawksight and sorry for coming back so late to this one. But good news is, with https://github.com/argoproj/argo-cd/pull/5038 now...

Hey @LS80, good point there. However, since it's the Helm template which constructs the final image name from the parameters given, are there any best practices documentation for Helm how...

Hey @LS80, sorry for coming back so late to this. I agree that probably the format you are refering (`sometag@sha256:somehash`) is the way to go forward for compatibility. I will...