3 ms·
Imagine 1,000s of helm charts. Your only abstraction tools are an umbrella chart or a library chart. There isn't much more in helm. I liked KRO's model a lot b
by CraigJPerry 11mo ago
Imagine 1,000s of helm charts. Your only abstraction tools are an umbrella chart or a library chart. There isn't much more in helm.
I liked KRO's model a lot but stringly typed text templating at the scale of thousands of services doesn't work, it's not fun when you need to make a change. I kinda like jsonnet plus the google cli i forget the name of right now, and the abstraction the Grafana folks did too but ultimately i decided to roll my own thing and leaned heavily into type safety for this. It's ideal. With any luck i can open source it. There's a few similar ideas floating around now - Scala Yaga is one.
- jodersky 11mo agoI'm curious what the google cli is that you're referring to. Could it be kubecfg (https://github.com/kubecfg/kubecfg https://github.com/kubecfg/kubecfg)? I've used it in the past (for a quite small deployment I must say), but have been very happy with it. Specifically the diff mode is very powerful to see what changes you'll apply compared to what's currently deployed.
- CraigJPerry 11mo agoYeah that's the one and the Grafana one is Tanka