flux2-kustomize-helm-example VS strimzi-kafka-operator

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)

Knative dashboards together with Kafka's dashboards it sheds light on almost any aspect of what's going on in the system.

Strimzi is an operator for deploying Kafka in K8s, and makes extensive use of CRs. E.g., https://github.com/strimzi/strimzi-kafka-operator/blob/0.31.1/examples/kafka/kafka-persistent.yaml

But I encountered a problem. In the example files they provide prometheus-additional.yaml file which is referred to in prometheus.yaml as additionalScrapeConfigs field. It collects Kubernetes node metrics for which it has panels in example Grafana dashboards. All good. But the problem is, the prometheus-additional.yaml file has a field called namespaces: names: [] (File can be seen here - https://github.com/strimzi/strimzi-kafka-operator/blob/main/examples/metrics/prometheus-additional-properties/prometheus-additional.yaml) in kubernetes_sd_configs.