ImageUpdateAutomation in namespace other than flux-default

[martijnjanssen]

Flux V2 is shaping up to be quite the tool, however from experimentation, there seem to be some crucial shortcomings with the ImageUpdateAutomation (and maybe also the ImagePolicy and ImageRepository). I have a deployment running in a non-default namespace (namespace: staging and not namespace: flux-system), the issue here is that the ImagePolicy and ImageRepository work and see the correct images. However, the ImageUpdateAutomation is unable to push changes to the gitrepository since it cannot reach the GitRepository, which is in the flux-system namespace and not in staging.

In addtion, since my architecture involves a staging and prod namespace, as of now, it seems that all three of the ImageUpdateAutomation, ImagePolicy and ImageRepository need to reside in both the prod and staging namespace, even though they affect the same image? Seems a bit overkill.

Maybe I'm misunderstanding internal dependencies of these components or I'm misreading the docs on configuring image updates. Regardless, to me it seems that it's not possible to do, of that the documentation is lacking.

If it's desired that I add my config I can do that, but I'm quite sure that it's not relevant in this case. The ImagePolicy and ImageRepository are working after all, while the ImageUpdateAutomation straight up has no access to the GitRepository resource which is created by bootstrap in the gotk-sync.yaml file.

[stefanprodan]

Duplicate of: #85

[martijnjanssen]

Whoops, terribly sorry!