feat: Trigger image update check on incoming webhook and/or other triggers

[jannfis]

Is your feature request related to a problem? Please describe.

Currently, ArgoCD Image Updater only polls container registries for new tags at a given interval. Depending on the number of images and registries to be checked, this can lead to an overwhelming number of requests and takes a lot of time.

Describe the solution you'd like

Update checks for images should also be triggered asynchronously, i.e. by a webhook on image push to the registry.

[ghostheory]

Per some of the constraints at my employer, this feature would be a game changer there. I was wondering if there is a timeline on this, and if there is anything I can do to help (unfortunately, I do not know Go).

[Ladorie]

Per some of the constraints at my employer, this feature would be a game changer there. I was wondering if there is a timeline on this, and if there is anything I can do to help (unfortunately, I do not know Go).

I second this feature. Would be very helpful for us as well.

[tylerbroadbent]

Same here! This would be a game changer and extremely valuable!

[joshdwads]

Serious game changer! This would be a great add.

[nikelsj11]

+1

[alexisbel1]

Game changer here!

[gastonborba]

Same here!

[tuananh]

@gastonborba i opened a PR earlier here. it's wip #284

[Disturbing]

Plz do this

[djfinnoy]

It would be amazing if the image updater could be triggered through the git webhook for refreshing argocd apps.

Git repositories POST to https://argocd.example.com/api/webhook, the image updater triggers for applications with annotations that match the git webhook. That way, all the user has to do is set some annotations, and then get a free ride with the existing ArgoCD git webhook functionality.

[tuananh]

git webhook is triggered very early in the CI process. at that moment, CI was just trigger and image is not built in.

the other information is git webhook payload doesn't have any information of the image tag, so image updater doesn't know which one to use for updating either.

[chenfli]

How about when the CI process completed the image creating it will send a web request to ArgoCD ? is it already implemented on Argo Events ?

[binhnguyenduc]

This would be a game changer for us as well. With a growing number of repositories and images, it takes quite sometime to update new image and it is slowing down our CD

[tuananh]

This would be a game changer for us as well. With a growing number of repositories and images, it takes quite sometime to update new image and it is slowing down our CD

Maybe you can continue on this pr https://github.com/argoproj-labs/argocd-image-updater/pull/284

[gain620]

Any updates on this feature?

[otherguy]

Would be amazing to have

[MrCorncob]

tracking hundreds of images and my GCP project has exceeded the Snapshot api limit, this feature is really really important imo

[victorbiga]

This could be the implementation of API request as /api/webhook?name=app-name, however this is thin line. Github Webhook currently does not support OIDC or any other ways of authenticating, therefore wanting for the new rollout to start by un-authenticated request or not is another question

[sidoverflow]

would love some updates on this @jannfis

[CreamyMiracle]

This would make things exponentially easier for us. Currently we are forced to do nasty tricks to achieve similar functionality.

[oubaydos]

+1