flux2-kustomize-helm-example VS addon-controller

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)

👏 Support this project Every contribution counts! If you enjoyed this article, check out the Projectsveltos GitHub repo. You can star 🌟 the project if you find it helpful.

Sveltos is an open-source Kubernetes project to deploy add-ons in a multitude of Kubernetes cluster. Sveltos can also be instructed to watch for changes in ConfigMaps and Secrets and triggers rolling upgrades for the associated resources, ensuring that applications stay up-to-date.

If you enjoyed this article, please check out the GitHub repo for the project. You can also star 🌟 the project if you found it helpful. The GitHub repo is a great resource for getting started with the project. It contains the code, documentation, and examples. You can also find the latest news and updates on the project on the GitHub repo. Thank you for reading!

And if you like it, please star ⭐ the project on GitHub

With projectsveltos, you can instruct add-on controller to deploy resources using Kustomize (on top of Helm charts and regular YAMLs). Then you could use its event-driven framework to deploy extra resources on demands.

When deploying add-ons with Sveltos Kuberntes add-on controller it is now possible to also enforce add-on constraints (defined in the management cluster using openapi).

Open a bug/feature enhancement on github

Here for instance https://github.com/projectsveltos/sveltos-manager/blob/main/.github/workflows/main.yaml

Documentation can be found here