flux2-kustomize-helm-example VS reliza-cli

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)

We currently provide accurate lead time and deployment frequency calculation capability via Reliza Hub - https://relizahub.com (operating in public preview). Since we track when each piece of code gets deployed to each environment and each instance. Other metrics are on our roadmap.

You then either leverage getlatestrelease functionality of reliza-cli - https://github.com/relizaio/reliza-cli#6-use-case-request-latest-release-per-project-or-product to request approved image or you can use replacetags functionality over your Dockerfile which would replace base image with the one approved - https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment

Note, we have recently released a new replacetags functionality (https://github.com/relizaio/reliza-cli#74-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-environment - going to add tutorial soon) so that you don't need to use templating language inside your helm charts or manifests and instead it would just parse raw base yamls into correct images per each environment.

We're building Reliza Hub for this purpose - https://relizahub.com

Note, it's somewhat outdated and we're working on a new one based on new replacetags functionality - https://github.com/relizaio/reliza-cli#72-use-case-replace-tags-on-deployment-templates-to-inject-correct-artifacts-for-gitops-using-instance-and-revision