Release description
We're happy to announce that starting with release v0.9.0, support for persisting changes to Git was added. Please be aware that using the Git write back feature will require Argo CD v2.0 and upwards.
Also, we are working towards a more "zero-conf" approach. For this, we have introduced a new way for interacting with Argo CD using the Kubernetes API. This removes the previous requirement of having to change your Argo CD configuration (e.g. creating a user, RBAC rules, etc) and we hope will make integration much easier for our users. This also has become the default. In order to use the Argo CD API, the --applications-api parameter must be explicitly set to argocd.
Upgrade from v0.8.0 is attached with a couple of required actions, please see below.
Upgrade notes (no really, you MUST read this)
-
Attention: By default,
argocd-image-updaternow uses the K8s API to retrieve applications, instead of the Argo CD API. Also, it is now recommended to install in the same namespace as Argo CD is running in (argocdby default). For existing installations, which are running in a dedicated namespace.To retain previous behaviour, set
applications_api: argocdinargocd-image-updater-configConfigMap before updating. However, it is recommended to move your installation into theargocdnamespace (or wherever your Argo CD is installed to) -
The permissions for the
argocd-image-updater-saServiceAccount have been adapted to allow read access to resources of typeSecretandargoproj.io/Application
Bug fixes
- fix: install missing git binary (#148)
- fix: run 'git add' for create files before pushing back (#143)
New features
- feat: support managing Application CRD using K8S client (#144)
- feat: Allow reuse of Argo CD repo credentials
- feat: Git write-back of parameters (#133)
Other changes
- refactor: make argocd-image-updater-config volume mapping optional (#145)