How do you keep Flux-managed charts and images updated?

November 19, 2026 5 answers
Asked by p.527+claspbadge

Flux is syncing my infrastructure from Git, but I haven't settled on an update strategy. My current Updatecli setup has conflicting patch, minor and major policies, and tags like 1.37.5-alpine cause comparison problems.

What works for tracking Helm chart and container image updates without making a small setup much more complicated?

Answers

Veldnaro+8t

Renovate is worth a look. Run it on a schedule in your Git CI and have it open changes for review. That keeps the version bumps in Git, where Flux can pick them up after they're merged.

For the alpine tag, Renovate's Docker versioning treats the suffix as a compatibility suffix, so it can propose a newer version while retaining alpine. Check that its file matching covers both your HelmRelease definitions and the files containing plain image references.

8p~fablelathe_639:

You can also use different rules for different dependencies, such as delaying a new release or automatically merging patch updates for low-risk targets.

Reply to this answer
Zeldrano-5v

Flux has image reflection and automation controllers if you want it to discover image updates and write changes back to Git. One possible split is Renovate for external dependencies and Flux image automation for internal application images. That's another moving part, though, so I wouldn't add it unless that split is useful to you.

Reply to this answer
_x94+zavmori.2

Watch the CRDs when bumping charts. Flux HelmReleases don't upgrade them by default, so a chart can move forward while its CRDs stay old. For releases that ship CRDs in the chart, look at setting spec.upgrade.crds to CreateReplace. Check the chart's upgrade guidance too.

Reply to this answer
Mivnaro-3x

Finding a new version is only half the job. Decide which updates you want to review and test before merging, and whether any are safe enough to merge automatically. A version bump in Git doesn't tell you by itself whether an upgrade will be safe for your setup.

Reply to this answer
Ravtixo-6j

If you want to keep working with Updatecli, separate scheduled jobs for different update problems may reduce some of the noise. It doesn't neatly solve conflicting policies, but it could be a smaller change than replacing the whole setup.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions