argocd-image-updater deployed. It currently supports only Kustomize and Helm (assuming it is seen in Argo as Helm), no raw grep+sed.
I advocate for standardizing on both (preferring Kustomize) #59.
To enable a repo for auto-updating (ft. rollbacks and git write-back 'upstreaming'), add to argocd/applications/<app>.yml:
metadata:
annotations:
argocd-image-updater.argoproj.io/image-list: my/image:^2 # 2.*.*
argocd-image-updater.argoproj.io/write-back-method: git # once it can be set globally, will be set globally
`argocd-image-updater` deployed. It currently supports only Kustomize and Helm (assuming it is seen in Argo as Helm), no raw grep+sed.
I advocate for standardizing on both (preferring Kustomize) https://git.k-space.ee/k-space/kube/issues/59.
To enable a repo for auto-updating (ft. rollbacks and git write-back 'upstreaming'), add to `argocd/applications/<app>.yml`:
```
metadata:
annotations:
argocd-image-updater.argoproj.io/image-list: my/image:^2 # 2.*.*
argocd-image-updater.argoproj.io/write-back-method: git # once it can be set globally, will be set globally
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
https://github.com/renovatebot/renovate
https://argocd-image-updater.readthedocs.io/en/stable/
argocd-image-updaterdeployed. It currently supports only Kustomize and Helm (assuming it is seen in Argo as Helm), no raw grep+sed.I advocate for standardizing on both (preferring Kustomize) #59.
To enable a repo for auto-updating (ft. rollbacks and git write-back 'upstreaming'), add to
argocd/applications/<app>.yml:Deployed, but needs annotations/impl to actually be useful.
edit: v1.0.0 released https://github.com/argoproj-labs/argocd-image-updater/releases
See also: #122
Bounty condition is for the system actually update and commit to git.
https://keel.sh/