Kubernetes Borg/Omega history topic 1: In Borg, Job Tasks were scheduled into Alloc instances, but almost everyone pinned groups of tasks into each instance. Often these were sidecars, such as for logging or caching.
-
Show this thread
-
It was clear that using such groups as the explicit primitive would be simpler. We called these "Scheduling Units". They were prototyped in Borg, but it was too hard to introduce new concepts. They became "SUnits" in Omega, and then Pods, as in a pod of peas or of whales, in K8s
1 reply 0 retweets 10 likesShow this thread -
We debated whether to embrace the containers-as-lightweight-VMs trend early in Kubernetes and just support one container per pod (initially called Tasks in the code), but I'm glad we didn't. One app per container unlocks the potential for more intelligent management.
2 replies 2 retweets 14 likesShow this thread -
Replying to @bgrant0607
Sadly it’s been difficult to remove the OS from the application :(
1 reply 0 retweets 0 likes -
Replying to @randomfrequency @bgrant0607
What *is* the OS, anyway? /cc
@bcantrill1 reply 0 retweets 1 like -
For Linux? http://Ld.so , libc, And misc gigabytes if utilities
2 replies 0 retweets 0 likes
It doesn't have to be. https://github.com/GoogleContainerTools/distroless …
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.