isopod
kubectl-neat-diff
Our great sponsors
isopod | kubectl-neat-diff | |
---|---|---|
4 | 1 | |
461 | 107 | |
0.4% | - | |
0.0 | 10.0 | |
5 months ago | over 1 year ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
isopod
-
Jsonnet – The Data Templating Language
Tried it[0], worked reasonably well. Be prepared for strong opposition from traditional “devops” folks “who don’t mind yaml” and will drag everyone down.
[0] - https://github.com/cruise-automation/isopod
- Deploying Kubernetes clusters in increasingly absurd languages
- YAML: It's Time to Move On
-
Cue: A new language for data validation
I like Cue and Jsonnet and Starlark and so on. But all of these have very low mindshare (though Starlark has the most momentum thanks to Bazel), and who knows if they will be dead by next year.
Being an early adopter is difficult both in terms of the immaturity of the tooling — Cue, for example, only has a Go implementation at the moment — and in terms of the risk of betting on an evolutionary dead end, which can cause a lot of unnecessary churn when you want to standardize on something across an entire organization.
As a concrete example, I'd love to replace Kubernetes's use of YAML with something like the above. But the tooling is immature, and almost nobody is using any of it. For example, there's Isopod [1], which is a nice-looking tool to use Starlark with Kubernetes. But it might go the same way as Ksonnet.
[1] https://github.com/cruise-automation/isopod
kubectl-neat-diff
-
Jsonnet – The Data Templating Language
Original creator of both of those here. I recommend just generating things out straight with the `jsonnet -m` command, and then doing `kubectl diff` on a PR and apply on merge. Scaled huge amount of infra this way and it’s easily understandable and extensible.
To clean up the diff a bit I recommend using: https://github.com/sh0rez/kubectl-neat-diff
Hope it’s helpful!
What are some alternatives?
skycfg - Skycfg is an extension library for the Starlark language that adds support for constructing Protocol Buffer messages.
github-desktop - A version of GitHub Desktop packaged with Conveyor
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
rules_jsonnet - Jsonnet rules for Bazel
ursonnet - experimental ur-cause tracer for jsonnet
kubecfg - A tool for managing complex enterprise Kubernetes environments as code.
hof - Framework that joins data models, schemas, code generation, and a task engine. Language and technology agnostic.
c2bf - Compiler from C to brainfuck
sprig - Useful template functions for Go templates.
jk - Configuration as Code with ECMAScript
nix - Nix, the purely functional package manager