Multi-namespace example

[jpds]

I use a single flux to manage deployments of the same applications across different namespaces. It might be any idea to showcase the multi-namespace features of kustomize rather than a flux per namespace with a different git-path:

• https://github.com/kubernetes-sigs/kustomize/blob/master/examples/multibases/multi-namespace.md

[tiagoveigalazaro]

Also trying to accomplish something similar to this. In our case we have multiple namespaces which can hold the same, some or different applications (sub-environments if you will).

Our current setup with kustomize is something like:

root
  |-  application A
                 |- base
                 |- namespace1
                 |- namespace2

We need this because sometimes, for example, we need to test two different instances of an external system.

But when using such a setup we get an error:

err="loading resources from repo: duplicate definition of '<cluster>:kustomization/"

So far we haven't found a solution to this, if someone has any pointers it would be really helpful.

[HerHde]

I'm also interested in this. Maybe it helps to mention that my logs spit out a bit more "detail":

caller=images.go:23 component=sync-loop error="getting unlocked automated resources: duplicate definition of '<cluster>:kustomization/' (in base/kustomization.yaml and namespace/test/kustomization.yaml)"

Maybe @stefanprodan has a clue?

[andrewmclagan]

We were guessing this is the core use-case for Flux. A little confused why this is not supported?