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.
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.
Helm tries to replicate the “apt get” package management experience, but as you may recall, that doesn’t work very well in the cloud. That’s why Config Management exists.
I think originally K8s was supposed to turn the cloud into one machine, but that dream hasn’t become reality. Instead we’re managing multiple clusters just like we managed multiple machines.
And instead of Config Management running away root on every machine, we’re building crazy complicated Progressive Delivery systems on top of Multitenant platforms, managing hundreds of Microservices across a fleet of clusters.
EVERYBODY PATCH NOW
• • •
Missing some Tweet in this thread? You can try to
force a refresh
