Jann Fischer

@jlbutler, glad to see that aws actually is trying to improve their public registry! Thanks for finding this issue, and asking for feedback! > is it OK for us to...

@jbutler We use the official Docker reference API (https://github.com/distribution/distribution) under the hood to perform pulling of manifests from a given image repository, to get details such as build dates and...

Yep, I agree. This would be a good feature to have.

I'm afraid that the only way to use Image Updater in combination with ApplicationSet is to use Git write-back. If you use the `argocd` write-back method, the Image Updater will...

I do understand this requirement, but it will most likely not be implemented in the code. I am not very familiar with GCE, and also don't have a test bed...

Hey @vikborisov, thanks for this PR. However, I feel that we should not move to yet another fork of `docker-registry-client`. Due to the staleness of both, the original repository and...

Me moved away from `docker-registry-client` to use Docker's `distribution/v3` API (see #249). Chances are, that this will enable oAuth support by default.

This is an interesting proposal. Config management plugins in Argo CD don't have a concept of parameters (yet), but do support setting environment variables. I think to implement support for...

This is because plugins are not supported. From the first paragraph of the README: > Currently it will only work with applications that are built using Kustomize or Helm tooling....

> I'm curious what's blocking it? https://github.com/argoproj-labs/argocd-image-updater/issues/168#issuecomment-803644040