flux2-kustomize-helm-example VS flux2-multi-tenancy

Any public repo show-casing a nice structure? (I am used to the Gitops world on K8s, and for the case of FluxCD for instance I would recommend this repo as a good practice to start multi-tenancy. https://github.com/fluxcd/flux2-kustomize-helm-example. I am looking for a similar "boilerplate" but for TF 😅)

My recommendation would be to take a look at their documented example of this exact scenario with various overlays for production and staging, but you could ofc add as many as you wanted. All you would do is for production point flux to the production overlay/ directory, which then calls all your normal files but overrides some values you desire. Further to this you can keep your helm chart focused on lets say the "most-common" use case, then just call it with whatever additional values you would like, E.G here in the same repo as above. Notice the values at the bottom of the yaml file which override the charts default values.

Here's an example using flux v2 to deploy to multiple environments/clusters: https://github.com/fluxcd/flux2-kustomize-helm-example

We are using flux2, which uses Kustomize under the hood. It takes a little bit of time to learn about the different CRD's which are available but once you do it works excellent. They also have an example project which sounds like it might fit your use case https://github.com/fluxcd/flux2-kustomize-helm-example

As /u/vincentdesmet mentioned Kustomize will most likely to solve your many "apps" with slightly difference issue, this is a good example https://github.com/fluxcd/flux2-kustomize-helm-example (also include helm one)

You may look at multi tenant deployment of fluxcd at https://github.com/fluxcd/flux2-multi-tenancy where you can have shared infrastructure repo to bootstrap flux with terraform (if you wish) and then a repo per team to manage k8s resources.

Bootstrap Flux v2 to the cluster via Gitlab CI then deploy everything else using their multi tenant approach - https://github.com/fluxcd/flux2-multi-tenancy

We are exploring this GitOps trend at Playtomic. We have two k8s clusters running using Flux and ArgoCD. We have a multi-tenancy setup, that is, one repo for the cluster itself, one repo for every application we deploy in the cluster. Flux and ArgoCD image updaters are in place.

Maybe this is helpful https://github.com/fluxcd/flux2-multi-tenancy