BCL is infamous inside google for being a very powerful footgun; jsonnet is a nice reboot of the idea, with a much saner semantics
For a while, BCL/GCL scoping rules were what my nightmares were made of.
Ksonnet: Simplify working with Kubernetes configurations
11–20 of 26 posts
Re: Ksonnet: Simplify working with Kubernetes configurations
#12I 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.
This looks very interesting, but there's not much info there, I guess without being able to login.
Re: Ksonnet: Simplify working with Kubernetes configurations
#13I 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.
This looks very interesting, but there's not much info there, I guess without being able to login.
I might regret this but you can login with: developer/developer
:) be nice!
Re: Ksonnet: Simplify working with Kubernetes configurations
#14Is 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.
If anyone is looking for the same, I made a quick docker image here: https://github.com/moondev/ksonnet-docker
Re: Ksonnet: Simplify working with Kubernetes configurations
#15Is 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.
If anyone is looking for the same, I made a quick docker image here: https://github.com/moondev/ksonnet-docker
[deleted]
Re: Ksonnet: Simplify working with Kubernetes configurations
#16Glad 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, lig…
can you point to some examples of this matsuri? I failed to figure out what it is from the link you pasted. A nice thing about jsonnet is that is it's a native data templating language, you don't have to compose a structured data format with a textual template language and deal with things as trailing commas in json or indentation (!!!) in yaml. It offers a sound model for extending and overriding values. Another thi…
Sorry, I don't have much in the way of examples. I am not using a textual template language. Instead, you define Ruby hashes which is then converted into either json (for loading into Kubernetes) or yaml (for debugging). It takes advantage of method overrides and class/module inheritance to achieve that. Specifications themselves are written as untyped, lazy-evaluated functional style. (Ruby being Ruby, it is not really immutable)
I just created a small example with redis: https://gist.github.com/hosh/89099f6f14ca5101e22c55f8d7f9e65...
That doesn't show off all of the features in there. There is a Rails-like convention so that resource definitions are loaded and can be referenced within each other. There are additional hooks that lets you generate `kubectl` commands, so for example, on our team, I defined hooks that lets me shell into a running container, or go directly to the console. (Redis, MongoDB, PostgreSQL, Rails, Rabbitmq, etc. consoles)
So yeah, Matsuri is very heavy-weight compared to Ksonnet. It isn't just that it is Ruby (already heavy-weight). Feature-wise, it does a lot more. I'm not sure that is a good or a bad thing.
Re: Ksonnet: Simplify working with Kubernetes configurations
#17Glad 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, lig…
[OP here] Another goal here is to have something that is easy to embed/repurpose. ruby is pretty heavyweight from that point of view. While jsonnet is a C program right now ( https://github.com/google/jsonnet ) we are looking at picking up work on a go port so it is easier to integrate with the kubernetes universe.
Looking forward to seeing the go port!
Re: Ksonnet: Simplify working with Kubernetes configurations
#18Earlier quoted context omitted.
This looks very interesting, but there's not much info there, I guess without being able to login.
I might regret this but you can login with: developer/developer :) be nice!
Wow, that's a huge piece of work. Unfortunately, I don't have the time to dig in deeply enough to truly appreciate it.
Re: Ksonnet: Simplify working with Kubernetes configurations
#19BCL is infamous inside google for being a very powerful footgun; jsonnet is a nice reboot of the idea, with a much saner semantics
For a while, BCL/GCL scoping rules were what my nightmares were made of.
Jsonnet simplifies scoping over bcl quite a bit. Specifically there is no up operator.
Re: Ksonnet: Simplify working with Kubernetes configurations
#20Earlier quoted context omitted.
I might regret this but you can login with: developer/developer :) be nice!
Wow, that's a huge piece of work. Unfortunately, I don't have the time to dig in deeply enough to truly appreciate it.
feel free to poke around when you have time, it is a very powerful platform...happy to give a demo session to you or a team if you're interested at some point.