does anyone at @Google past or present know when the concept of ‘pods’ as a unit of deployed processes originated?
-
Show this thread
-
Replying to @littleidea @Google
At least one of these guys know:
@jbeda@cmcluck@brendandburns@thockin@bgrant06071 reply 0 retweets 7 likes -
Replying to @stephenaugustus @littleidea and
It was loosely based on a concept in Borg called an alloc. It is simplified though. But we focused on the most common usage of alloc around running colocated containers. We didn't call them sidecars yet but there were similar ideas being used and incubated.
2 replies 4 retweets 28 likes -
Replying to @jbeda @stephenaugustus and
I think I proposed the shared network namespace and ip per pod along with the per container filesystem/chroot. It might have been Tim though. Lots of bikeshedding to come up with the name Pod.
1 reply 1 retweet 16 likes -
Replying to @jbeda @stephenaugustus and
Originally we got a ton of pushback on it as people didn't get it. Had to hack it into docker with pause container. It was only after there were common sidecars that it clicked for folks. Docker issue from 2014 is still open.https://github.com/moby/moby/issues/8781 …
2 replies 2 retweets 43 likes -
Replying to @jbeda @stephenaugustus and
Borg "alloc" -> Omega "scheduling unit" -> Kubernetes "pod". The name itself was from a brainstorm. Docker's logo is a whale. A group of whales is called a ... Also, it was short. The network model was explored in Borg a few years prior, but wasn't feasible at the time.
8 replies 41 retweets 192 likes -
Anyone know when alloc was born? Was this capability an epiphany or an accretion? If this isn’t lost to history, I would love to do the archeology.
4 replies 2 retweets 7 likes
Alloc was already present in the very first commit of the Borg API at the beginning of 2004.
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.