Replies: 1 comment
-
I think you might have namespaces of the ImageRepository and ImagePolicy backwards - assuming your GitRepository and ImageUpdateAutomation objects are in the flux-system namespace, then the ImagePolicy should also be in the flux-system namespace and the ImageRepository should be in the "app" namespace. But even after making that change I am having an issue with the ImagePolicy not reconciling the image tags that the ImageRepository is pulling. After playing around with it for a while, I noticed that restarting the image reflector controller will cause the cross namespace ImagePolicy to be reconciled exactly once, but any new tags pushed to the image repository are completely ignored. Looking through the image reflector controller logs (level=debug) I confirmed that the controller will only reconcile ImagePolicy objects using cross namespace references shortly after the controller starts up and then completely ignores them unlike the ImagePolicy objects that are NOT using the cross namespace references. I'm thinking either the documentation is missing something extremely crucial in order to get this to work or there is a bug. Also I apologize in advance for not sharing the logs as they are work related. |
Beta Was this translation helpful? Give feedback.
-
At first, I deployed
ImageRepository
andImagePolicy
together influx-system
namespace and it was working fine.example
Now, I'm trying to follow this guide
https://fluxcd.io/docs/components/image/imagerepositories/#allow-cross-namespace-references
So that I can track them in separate namespaces.
But when I do that the new imagePolicy hang at
waiting to be reconciled
example
I tried using
kubectl describe
,flux logs
andflux trace
but can't figure out what is wrong. Does kustomizations need to be in the same namespace asImagePolicy
? That is the only thing I can guessThank you for your helps
Beta Was this translation helpful? Give feedback.
All reactions