We have a requirement to deploy an instance of an app per environment. Each environment has its own namespace within a shared cluster. Our current setup makes use of folders - each environment has its own folder as well as a Flux Kustomization pointing to this folder. Although, we make use of Kustomize overlays, there is still a lot of repetition/boiler plate code across the environments. We were hoping to reduce this, by having a single environment template folder, which is the path used by each environment’s Flux Kustomization and take advantage of the targetNamespace attribute to have resources created in the environment’s specific namespace. We would also make use of the patch attribute in each environment’s Flux Kustomization to patch the template resources if needed.

Looking at the source code of the Kustomize controller, it seems a temporary folder is created in the reconcile step for each Flux Kustomization. This is where we believe the end manifests are built. We therefore, assume that there shouldn’t be any issues in adopting the above approach, however we are not sure if we have missed anything - especially considering that this could be alternative approach to what ResourceSets offer. Unlike ResourceSets, the proposed setup should not only allow us to have multiple Flux Kustomzation’s per environment with dependencies but also support multiple environments at the same time.

Any help would be appreciated. Thanks.