k-Uber-net-s rhymes well with global domination.
To the Kubernetes devs: It's probably worth mentioning that somewhere in the Readme. I say that partially because as an end user it's nice to know you're building on solid building blocks that have stood the test of time, and also because it was moderately disheartening to learn about Kubernetes with no mention of Salt and then later learn that it was build partially on the hard work of the Salt team.
Using their project as a building block is great, but give credit where it's due.
[1]: http://research.google.com/pubs/pub41684.html [2]: https://www.youtube.com/watch?v=XsXlm4wmB6o
I wonder if anyone in here can comment on whether that is indicative of a trend inside Google - are people writing less Python / Java in there these days?
I don't know about "less Python/Java", but Go has been on the rise at Google internally, and has been used in public-facing services for a while.
dl.google.com (which powers Chrome downloads) and the MySQL database management layer for Youtube[0] have both been written in Go for a while now.
If we look at a very high level sketch of what a dynamic cluster system look like (https://speakerdeck.com/jbeda/containers-at-scale?slide=5) I think that CoreOS fits in at the "Managed Base OS" level.
Kubernetes is a Cluster Scheduler and a "Node Container Manager" (called the kubelet in Kubernetes).
(This deck is pre-Kupernetes. The python agent that we released will be replaced with the kubelet at some point soon.)
