3 ms·

Disclosure: I work at Google on Kubernetes We _absolutely_ want to push Kubernetes to be "gmail-easy" - here's a recent demo: https://www.youtube.com/watch?v=

Disclosure: I work at Google on Kubernetes We _absolutely_ want to push Kubernetes to be "gmail-easy" - here's a recent demo: https://www.youtube.com/watch?v=Bv3JmHKlA0I https://www.youtube.com/watch?v=Bv3JmHKlA0I If you don't feel like watching a video, here's the commands to get a fully production-ready cluster going: master# apt-get install -y kubelet master# kubeadm init master Initializing kubernetes master... [done] Cluster token: 73R2SIPM739TNZOA Run the following command on machines you want to become nodes: kubeadm join node --token=73R2SIPM739TNZOA <master-ip> node# apt-get install -y kubelet node# kubeadm join node --token=73R2SIPM739TNZOA <master-ip> Initializing kubernetes node... [done] Bootstrapping certificates... [done] Joined node to cluster, see 'kubectl get nodes' on master. All certs, all configurations, etc - done. No bash, no mess. All you need is a package manager and docker (or your container runtime of choice) installed. If you have thoughts on how we should do it better, PLEASE join us! https://github.com/kubernetes/community/tree/master/sig-cluster-lifecycle https://github.com/kubernetes/community/tree/master/sig-clus...

raesene9 10y ago
I think one of the challenges for me in learning Kubernetes is that the a lot of the tutorials do take a quite "run this script and things happen" approach which is great in that it gets you up and running quickly, but is less good for understanding what's under the hood, which is really needed before some people will feel fully comfortable with the technology. Obviously there's Kelsey Hightower's great Kubernetes the hard way tutorial, but even there some details are quite GKE specific. It'd be nice to see some tutorials that make no assumptions about running on a specific cloud provider or using automated tools to bootstrap the cluster.
- TheIronYuppie 10y ago
  Oh, for sure! Being totally script free (and cloud neutral) is the goal of this effort. As you see above, there's absolutely ZERO script/bash/automation/etc.
  - harlowja 10y ago
    I have a somewhat confused feeling that your definition from above of 'fully production-ready cluster' is different than mine and others ;)
brudgers 10y ago
I appreciate your thoughts. My suggestion is to design an interface for Kubernetes in ways less reflective of Conway's Law. That's how the needle moves from 'solution' toward 'product'. In essence, that's what I think 'Gmail Easy' boils down to. Gmail has user stories that are based on people (much)+ less technically sophisticated than a new fresh from school Google SRE. I think that the call to action suggests why Docker is pursuing Swarm. In a decade of container orchestration development, creating a good onboarding experience with the diverse demographic of Docker users has never been a priority within Google. If it had been a priority, Gmail-easy Kubernetes integration might have long since been a pull request from Google. That's what it says right on the label of the open-source software can. The talk about forking Docker seems consistent with the absence of pull requests. It's just another business decision.

raesene9 10y ago

I think one of the challenges for me in learning Kubernetes is that the a lot of the tutorials do take a quite "run this script and things happen" approach which is great in that it gets you up and running quickly, but is less good for understanding what's under the hood, which is really needed before some people will feel fully comfortable with the technology. Obviously there's Kelsey Hightower's great Kubernetes the hard way tutorial, but even there some details are quite GKE specific. It'd be nice to see some tutorials that make no assumptions about running on a specific cloud provider or using automated tools to bootstrap the cluster.

TheIronYuppie 10y ago
Oh, for sure! Being totally script free (and cloud neutral) is the goal of this effort. As you see above, there's absolutely ZERO script/bash/automation/etc.
- harlowja 10y ago
  I have a somewhat confused feeling that your definition from above of 'fully production-ready cluster' is different than mine and others ;)

brudgers 10y ago

I appreciate your thoughts. My suggestion is to design an interface for Kubernetes in ways less reflective of Conway's Law. That's how the needle moves from 'solution' toward 'product'. In essence, that's what I think 'Gmail Easy' boils down to. Gmail has user stories that are based on people (much)+ less technically sophisticated than a new fresh from school Google SRE. I think that the call to action suggests why Docker is pursuing Swarm. In a decade of container orchestration development, creating a good onboarding experience with the diverse demographic of Docker users has never been a priority within Google. If it had been a priority, Gmail-easy Kubernetes integration might have long since been a pull request from Google. That's what it says right on the label of the open-source software can. The talk about forking Docker seems consistent with the absence of pull requests. It's just another business decision.