# argocd-image-updater

argocd-image-updater is a self-hosted development app. A Helm chart for Argo CD Image Updater, a tool to automatically update the container images of Kubernetes workloads which are managed by Argo CD It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4674/argocd-image-updater

## Description

A Helm chart for Argo CD Image Updater, a tool to automatically update the container images of Kubernetes workloads which are managed by Argo CD

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

62/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 1 day ago)
- Popular: 65 (1,734 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 20 (1 serious finding, 4 minor, CI, tests, OpenSSF Scorecard 5.7/10)

## Security check

1 serious finding: A GitHub workflow can be triggered by outsiders to run their code with the project's secrets.
Automated checks on commit 668e8c5, 24 Oct 2026. Not an audit.

## Links

- Documentation: https://argocd-image-updater.readthedocs.io
- Kubernetes (Helm): https://artifacthub.io/packages/helm/argo/argocd-image-updater
- Official website: https://argocd-image-updater.readthedocs.io/en/stable/
- GitHub: https://github.com/argoproj-labs/argocd-image-updater

## Common questions

### Will argocd-image-updater work with plain YAML Argo CD applications?

No, it currently only supports Argo CD applications built with Kustomize, Helm, or a Config Management Plugin. Plain YAML applications are not supported.

### Why does it create .argocd-source-<app_name>.yaml files in my Helm chart directory?

It can create .argocd-source-<app_name>.yaml files in Helm chart directories. This behavior can complicate reusing the same chart across multiple clusters.

### Why are image-updater changes rolled back immediately by Argo CD?

A self-healing app-of-apps can roll back the updater's changes immediately. In the reported case, ignoreDifferences could not override that self-healing behavior.

### What should I check if it detects a new tag but does not sync?

Check annotation errors, registry authentication, Git write-back configuration, and Argo CD sync failures. These are common causes when a new tag is detected but the Application is not updated.

---
Source: Our Local Host (https://ourlocalhost.com/app/4674/argocd-image-updater), the self-hosted and open-source app directory.
