4 ms·
Kubernetes itself doesn't have a steep learning curve. Setting up and configuring a Kubernetes cluster by hand does have a steep learning curve. I had spent mo
by hosh 11y ago
Kubernetes itself doesn't have a steep learning curve.
Setting up and configuring a Kubernetes cluster by hand does have a steep learning curve. I had spent more time trying to get Kubernetes up and running than I have actually using it.
Actually using Kubernetes is fairly straight-forward (once you get it up and running). It solves many of the pain points with seriously using containers in a development workflow. Though, I ended up writing a Ruby framework to bridge the gap -- but that's the point. Kubernetes exposes a set of primitives onto which I can build on top of. So I'm not entirely sure where the "opinionated" bit comes from.
- jcastro 11y agoWe're working on making Kubernetes easily deployable on Ubuntu, we just had a session on this today if you want to check out the state of things: https://www.youtube.com/watch?v=aj76OeBjxpk https://www.youtube.com/watch?v=aj76OeBjxpk Our goal is to make the deployment bits production ready for 16.04, and I'm sure $your_favorite_os_vendor is probably doing the same thing.
- hosh 11y agoThat's great to hear. I initially installed Kubernetes via the hypercube containers on my dev ubuntu box ... but I have found that some key pieces really should be built in (flanneld, early docker). Of course, with Docker 1.9 out, you guys probably want to support that too :-D For staging, I ended up using CoreOS. I didn't want to use any of the existing scripts to deploy k8s on ubuntu, and I didn't want to write my own Chef recipes. I was a bit intimidated by CoreOS at first, but it has been a great experience ... except when it wasn't :-D.