How do you keep image and chart updates manageable with Argo CD?

November 18, 2026 5 answers
Asked by 8r!parcelcog_237

My ApplicationSets manage both cluster services and application deployments, but chart versions and image tags are starting to get stale. I also need to detect new OCI artifacts, including migration images.

Kargo looks useful but verbose for a simple tag change, and Argo CD Image Updater seems to add a lot of annotations. What patterns work for keeping updates reviewed and moving them through environments?

Answers

_b58+drimvelo.4

Renovate is a good starting point for the stale dependency problem. Run it on a schedule and let it open pull requests for chart versions, container images, and other supported dependencies in Git. Your normal build and validation checks can run on those requests before anything is merged.

For an unusual tag field like the migration image, a custom regex manager may be needed so Renovate knows what to look for and where to find newer versions. That can be less work than maintaining a separate clone, edit, commit, push, and pull request workflow for every tag.

8r!parcelcog_237:

How would you handle different versions in staging and production?

9m+drivnexa_682:

Keep the desired version for each environment in Git and decide separately how a tested version gets promoted to production. A dependency update tool can propose changes, but it does not by itself define your promotion policy.

Reply to this answer
Nuvdari-5x

I would split third-party maintenance from your own release flow. Renovate or Dependabot can propose dependency bumps for things like cert-manager. Kargo is more compelling when you want to move your own freshly built image through staging and onward after validation.

That does mean accepting some Kargo configuration. Whether it is worth it depends on how much promotion and testing logic you need, not just how many lines it takes to change one tag.

Reply to this answer
2j+fexnaro_594

Take a look at OCI-packaged Helm charts too. One approach is to package the application configuration with the chart and update the chart reference in the ApplicationSet. That gives you a versioned package to promote, though you still need to decide how image versions and environment-specific values are represented.

4j+gimbalspool_628:

That changes what you update, rather than eliminating updates. Make sure the chart version actually identifies the image and configuration you intend to deploy.

Reply to this answer
_a64~vexnaro.8

Updatecli is another option if the standard dependency managers do not fit your custom artifacts. It runs in CI and takes update policies from YAML, so it may be worth comparing against a custom Renovate manager before building a bespoke pipeline.

Reply to this answer
_n38~keldravi.6

For operator upgrades, detecting a newer chart is only the first step. Check the chart and values for incompatible changes, then validate the proposed update before merging. A canary can be useful for changes that need more confidence, but not every dependency needs the same rollout process.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions