It's not that critical to the project itself, just naming and discoverability.
Ksonnet: Simplify working with Kubernetes configurations
21–26 of 26 posts
Re: Ksonnet: Simplify working with Kubernetes configurations
#22Earlier quoted context omitted.
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.
Re: Ksonnet: Simplify working with Kubernetes configurations
#23jsonnet 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.
Re: Ksonnet: Simplify working with Kubernetes configurations
#24Is 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.
Re: Ksonnet: Simplify working with Kubernetes configurations
#25BCL is infamous inside google for being a very powerful footgun; jsonnet is a nice reboot of the idea, with a much saner semantics
Can I use ksonnet without knowing what the generated YAML looks like? If I still have to fully understand the underlying YAML formats, then using ksonnet just increases the cognitive load.
I think a parallel is say you decide to use TypeScript since it is all the rage;. But when you try to learn it, most docs says if you do this in TypeScript, this really happens in JS. Now, you need to know both TS & JS to do your job. This is why I personally never found coffeescript etc simpler JS exciting.
Re: Ksonnet: Simplify working with Kubernetes configurations
#26BCL is infamous inside google for being a very powerful footgun; jsonnet is a nice reboot of the idea, with a much saner semantics
I thought I was done with BCl/GCL when I left Google. But I guess there is no escape from it. BCL has really weird late binding behavior, very little tooling support. Can I use ksonnet without knowing what the generated YAML looks like? If I still have to fully understand the underlying YAML formats, then using ksonnet just increases the cognitive load. I think a parallel is say you decide to use TypeScript since it…
Previous efforts at "simplifying" k8s make you choose between one or the other use-case. ksonnet is trying to provide something that can be more continuous along this spectrum. .. At least that's the hope.