I am experiencing an odd behavior of IAC.
I expected IAC to be triggered by an update from an ImageRepository object, and to commit to my repository the updated tag.
This only works if I manually trigger a reconciliation.
Steps to reproduce
Install flux with image automation controller and image reflector controller
The GitRepository above is the same repo used to bootstrap flux in the cluster.
The cluster uses k3s on a 3 master + workers configuration.
To test the behavior I chose policy.alphabetical.order: asc then I tagged the httpbin image as atest, btest, ctest etc.
flux version is v.2.3.0
What happens is that ImageRepository correctly gets latest tags
The ImagePolicy is missing the labels you've set in the ImageUpdateAutomation, so I'm very surprised it works when you run reconcile, it should never update the repo.
Describe the bug
I am experiencing an odd behavior of IAC. I expected IAC to be triggered by an update from an ImageRepository object, and to commit to my repository the updated tag. This only works if I manually trigger a reconciliation.
Steps to reproduce
The
GitRepository
above is the same repo used to bootstrap flux in the cluster. The cluster uses k3s on a 3 master + workers configuration. To test the behavior I chosepolicy.alphabetical.order
:asc
then I tagged the httpbin image as atest, btest, ctest etc. flux version is v.2.3.0What happens is that ImageRepository correctly gets latest tags
ImagePolicy matches the latest tag
ImageUpdateAutomation says the repository is up to date but it doesn't push any update to the git repository
If I then run
flux reconcile
against ImageUpdateAutomation , then boom: image automation controller pushes the commit toward the repositoryI am probably missing something and I am hopeful that @stefanprodan will be able to give me the correct nudge to get this sorted
Expected behavior
I was expecting IAC to automatically push the commit to the repo without manual reconciliation
Screenshots and recordings
No response
OS / Distro
N/A
Flux version
flux: v2.3.0
Flux check
► checking prerequisites ✗ flux 2.3.0 <2.4.0 (new CLI version is available, please upgrade) ✗ Kubernetes version v1.24.17+k3s1 does not match >=1.28.0-0 ► checking version in cluster ✔ distribution: flux-v2.3.0 ✔ bootstrapped: true ► checking controllers ✔ helm-controller: deployment ready ► ghcr.io/fluxcd/helm-controller:v1.0.1 ✔ image-automation-controller: deployment ready ► ghcr.io/fluxcd/image-automation-controller:v0.38.0 ✔ image-reflector-controller: deployment ready ► ghcr.io/fluxcd/image-reflector-controller:v0.32.0 ✔ kustomize-controller: deployment ready ► ghcr.io/fluxcd/kustomize-controller:v1.3.0 ✔ notification-controller: deployment ready ► ghcr.io/fluxcd/notification-controller:v1.3.0 ✔ source-controller: deployment ready ► ghcr.io/fluxcd/source-controller:v1.3.0 ► checking crds ✔ alerts.notification.toolkit.fluxcd.io/v1beta3 ✔ buckets.source.toolkit.fluxcd.io/v1beta2 ✔ gitrepositories.source.toolkit.fluxcd.io/v1 ✔ helmcharts.source.toolkit.fluxcd.io/v1 ✔ helmreleases.helm.toolkit.fluxcd.io/v2 ✔ helmrepositories.source.toolkit.fluxcd.io/v1 ✔ imagepolicies.image.toolkit.fluxcd.io/v1beta2 ✔ imagerepositories.image.toolkit.fluxcd.io/v1beta2 ✔ imageupdateautomations.image.toolkit.fluxcd.io/v1beta2 ✔ kustomizations.kustomize.toolkit.fluxcd.io/v1 ✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2 ✔ providers.notification.toolkit.fluxcd.io/v1beta3 ✔ receivers.notification.toolkit.fluxcd.io/v1 ✗ check failed
Git provider
GitHub
Container Registry provider
quay.io
Additional context
No response
Code of Conduct