The ArgoCD project has announced a brand-new release of Argo CD Image Updater, the companion controller to Argo CD.
This tool streamlines continuous delivery by automatically monitoring container registries and updating container images in Argo CD applications, eliminating the need for custom pipelines to update Kubernetes manifests.
This release introduces 6 new features, 16 fixes, and several documentation updates. Here are the key highlights:
Key Features in This Release
1. Support for Non-Default Namespaces
Previously, Argo CD Image Updater only supported applications in the default argocd namespace. Now, it works with applications deployed in any namespace, offering greater flexibility.
2. Preserve Field Order in Kustomize Updates
When updating container images in Kustomize applications via Git write-back, field order inconsistencies often cause unnecessary changes in git diff. The updater now preserves field order, ensuring smoother automation and compatibility with external tools.
3. Updating Multiple Images in Helm Value Files
For Helm applications containing multiple container image references, Argo CD Image Updater now properly detects and updates all relevant images, not just one. This ensures the expected behavior for multi-image Helm applications.
4. Compatibility with Disabled Auto-Sync
Organizations that disable auto-sync in Argo CD (e.g., for manual production deployments) can now use Argo CD Image Updater effectively. The updater will perform image updates once without falling into a repetitive update loop.
5. Support for Multi-Source Application Sets
Argo CD Image Updater now supports multi-source applications and Application Sets by detecting the type of each application from its status field. This enables seamless image updates even in complex application configurations.
6. Improved Release Process and Unit Testing
We’ve introduced enhancements to integration testing and contributor workflows, making it easier for new developers to contribute. These changes ensure smoother onboarding and a better development experience.
To contribute new features, submit a pull request on GitHub. If you encounter any issues, connect with us on the #argo-cd-image-updater channel in the CNCF Slack. Interested in becoming a maintainer? Reach out via the #argo-cd-contributors channel.
