I feel like the KEP was never examined "adversarially". And that isn't the right word, because nobody wants to create conflict where there is none. Perhaps "skeptically" is a better word, but even that implies some…
Making an "easier" app-level experience very quickly becomes (necessarily) opinionated, because you need to anticipate which k8s parameters need to be exposed and which can be derived/assumed. Narrowing the…
The fork is my fault. I agree it's confusing. I wrote (and still maintain) kubecfg. Heptio joined the project and started adding lots of great stuff. Eventually it was clear they wanted to take it in a direction that…
I wrote kubecfg as an unashamed imitation of borgcfg, because for all that we like to complain - borgcfg + GCL + git works extraordinarily well. Kubecfg uses jsonnet, which is similarly openly inspired by GCL (but with…
That's not quite true. More parts == more things that can fail, but whether those failures result in the entire system failing depends on how you've combined the parts. If you make each of the pieces required parts of…
^ This.
If it's helpful at all, here's a concrete example of a k8s nginx setup that exports-to/is-monitored-by prometheus: https://github.com/bitnami/kube-manifests/blob/master/common... (Start at…
If you (and others on this sub-thread) like managing kubernetes through version control, I humbly suggest trying out the ksonnet/kubecfg toolchain (https://github.com/ksonnet/kubecfg and the closely related…
The idea is that we can support both simultaneously: - people who want/need full expressiveness can do that, and - people who don't need that can happily use higher-level templates that someone else has put together.…
It's "alpha", as the version signifies - but there's a linux/x86-64 binary of 'kubecfg' you can play with on https://github.com/ksonnet/kubecfg/releases
I feel like the KEP was never examined "adversarially". And that isn't the right word, because nobody wants to create conflict where there is none. Perhaps "skeptically" is a better word, but even that implies some…
Making an "easier" app-level experience very quickly becomes (necessarily) opinionated, because you need to anticipate which k8s parameters need to be exposed and which can be derived/assumed. Narrowing the…
The fork is my fault. I agree it's confusing. I wrote (and still maintain) kubecfg. Heptio joined the project and started adding lots of great stuff. Eventually it was clear they wanted to take it in a direction that…
I wrote kubecfg as an unashamed imitation of borgcfg, because for all that we like to complain - borgcfg + GCL + git works extraordinarily well. Kubecfg uses jsonnet, which is similarly openly inspired by GCL (but with…
That's not quite true. More parts == more things that can fail, but whether those failures result in the entire system failing depends on how you've combined the parts. If you make each of the pieces required parts of…
^ This.
If it's helpful at all, here's a concrete example of a k8s nginx setup that exports-to/is-monitored-by prometheus: https://github.com/bitnami/kube-manifests/blob/master/common... (Start at…
If you (and others on this sub-thread) like managing kubernetes through version control, I humbly suggest trying out the ksonnet/kubecfg toolchain (https://github.com/ksonnet/kubecfg and the closely related…
The idea is that we can support both simultaneously: - people who want/need full expressiveness can do that, and - people who don't need that can happily use higher-level templates that someone else has put together.…
It's "alpha", as the version signifies - but there's a linux/x86-64 binary of 'kubecfg' you can play with on https://github.com/ksonnet/kubecfg/releases