Skip to content
Latchkey

Flux ImagePolicy "no image found" in CI

image-reflector-controller scanned the registry and image-automation applied the ImagePolicy, but the policy matched no tag. The ImageRepository has no scanned tags, or the policy filter and range exclude every tag.

What this error means

An ImagePolicy reports "False" with "no image found" and image automation does not produce an update because there is no selected tag.

image-automation-controller
no image found for policy

Common causes

The ImageRepository has no scanned tags

The referenced ImageRepository failed to scan (bad auth or wrong image name), so there are no tags for the policy to select from.

The filter or range excludes every tag

A filterTags pattern or semver range does not match any published tag, so the policy selects nothing.

How to fix it

Fix the scan and the policy selection

  1. Confirm the ImageRepository scanned tags; fix its credentials or image name if not.
  2. Adjust the policy filter or semver range to match real tags.
  3. Reconcile the image resources.
Terminal
flux get image repository web
flux get image policy web
flux reconcile image repository web

Verify the filter matches published tags

List the scanned tags and confirm the filterTags pattern and range actually select one.

Terminal
kubectl -n flux-system describe imagepolicy web

How to prevent it

  • Keep the ImageRepository credentials valid so tags scan.
  • Write filterTags patterns and ranges that match your tag scheme.
  • Verify a new tag scheme selects at least one image before relying on automation.

Related guides

Run this faster and cheaper on Latchkey managed runners. Start free →