Having put some time into #Kustomize now, I think it's probably a better solution than Helm for building permutations of configs for multiple clusters and environment.

It also makes it easier to integrate upstream config changes, because you're just applying patches/mixins. Plus, you can also just render Helm charts with default values, and then apply Kustomizations afterwards. So you can still take advantage of published Helm charts, as long as they're just templating and don't use the advanced features like hooks.

Has anyone yet written a compiler that will allow me to bundle bash with a makefile entrypoint into a distributable binary?

I’m fairly convinced that hard multi-tenancy within a single k8s cluster is a use case it wasn’t designed for. The harder I try to reduce the blast radius of potentially compromised service components, the harder it becomes to justify the effort.

#Spinnaker may be popular, but it has HUGE hidden cost when using with/on #Kubernetes.
1. The primitives are all IaaS-based
2. Many config changes require admin management and halyard reboot, meaning you need continuous deployment for your continuous deployment 3. There’s no abstraction for container platform in spinnaker, so you have to have a new “account” per k8s
4. There’s no namespace abstraction in Spinnaker, so you need a new account for each cluster+namespace permutation.