This links to a blog post that is mostly marketing fluff and quotes from fawning CTOs. Useful documentation and examples are here: http://ksonnet.heptio.com

BCL is infamous inside google for being a very powerful footgun; jsonnet is a nice reboot of the idea, with a much saner semantics

Glad someone put in the effort for this.

I wrote something that fills this econiche sometime last year in Ruby (https://github.com/matsuri-rb/matsuri). Same ideas: mixins, generation of Kubernetes resources, etc. For better or worse, it also adds the idea of combining all the deployment environments into a single workflow and command line interface.

The big difference? Ksonnet is better documented and promoted, lighter-weight, and now better supported within the community.

jsonnet is great. We've been using it at my company to generate our configurations for ElasticBeanstalk, Terraform, and other various auxiliary services.

We've been looking into moving towards Kubernetes. I'm looking forward to seeing if ksonnet can fit our needs.

I have been working on a UI based system for managing these configurations in a way that doesn't rely on any particular syntax but allows you to construct object graphs (that is what they all boil down to) directly: http://blog.crudzilla.com/2016/10/managing-configurations-wi...

I will be interested in feedback on how such an approach could be helpful in managing complex configurations.

Is there a dockerhub image or linux binary available? Trying to figure out the context of best way to use this in a job. Currently have been using containerized https://github.com/andreasjansson/envtpl in my builds and been pretty happy with it.

nit/rant: I think it would've been better if JsonNet was named differently, since there is "Json.Net" and googling for "JsonNet" find it (or looking at say ht.algolia.com).

It's not that critical to the project itself, just naming and discoverability.