4 ms·
If you like those, I'd take a look at Grafana's Tanka [0]. It also uses jsonnet but has some additional features such as showing a diff of your changes before y
by threentaway 6y ago
If you like those, I'd take a look at Grafana's Tanka [0]. It also uses jsonnet but has some additional features such as showing a diff of your changes before you apply, easy vendored libraries using jsonnet-bundler, and the concept of "environments" which prevents you from accidentally applying changes to the wrong namespace/cluster.
[0] https://github.com/grafana/tanka https://github.com/grafana/tanka
- q3k 6y agoI looked at it, I don't like it for the same reason as I dislike many other tools in this space: it imposes its own directory structure, abstraction (environments) and workflow. I'm a fan of the kubecfg-style approach, where it lets you use whatever sort of structure makes sense for you and your project. It's a 'framework' vs 'library' thing, but in the devops context.
- dilyevsky 6y agoI worked on this at previous gig - https://github.com/cruise-automation/isopod https://github.com/cruise-automation/isopod Same use-case but uses Starlark dsl instead of jsonnet