While I love the comic and the idea of telling this story more widely, I do want to correct some of the details in this comic. It is important for community health that we don't overplay the history here.
-
Show this thread
-
1) Kubernetes is a infrastructure management framework and not an application itself. 2) While software is written for multiple computers the way it is deployed isn't.
1 reply 1 retweet 15 likesShow this thread -
3) "Engineers came up with containers" glosses over a *ton* of work across Solaris, FreeBSD, Linux kernel, docker, etc. There is history here.
1 reply 2 retweets 18 likesShow this thread -
4) I didn't help create borg. I used it. I did help create GCE -- and that used borg. 5) Kubernetes is inspired by borg but isn't a renamed borg. 6) Docker can both be seen as a competitor (Swarm) and a partner/component (containerd).
2 replies 4 retweets 31 likesShow this thread -
Wrt creating k8s -- it was me,
@cmcluck and@brendandburns that got the project started. Early on@nastyfinn,@bgrant0607 and@thockin came on board to help shape project early.1 reply 2 retweets 14 likesShow this thread -
7) It is great to see Phillips move from 3s to 200ms. But k8s is only part of the puzzle. All the magic happens with what people are building ON TOP of k8s. /end
1 reply 1 retweet 13 likesShow this thread -
One more thing! Early on Kubernetes saw a huge boost from the redhat OpenShift team led by
@smarterclayton. The project is much better because of their early involvement.1 reply 39 retweets 72 likesShow this thread -
The origin story is more nuanced than the "co-creator" brush I get painted with. The project would be WILDLY different and less successful without RH and several other key early voices.
2 replies 14 retweets 56 likes -
"Added features to borg and renamed it Kubernetes" LOL, not really. Still very entertaining though.
1 reply 0 retweets 6 likes -
Replying to @originalavalamp @thockin and
Who gets credit for saying no to borgcfg?
2 replies 0 retweets 2 likes
Not just one person, but an early writeup:http://prs.k8s.io/1007
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.