I've been meaning to share more of Kubernetes's Borg & Omega heritage, but haven't been able to find time. I'll try one feature/idea at a time. Topics in my list include K8s architecture, API model, labels, annotations, pods, watch, controllers, apply, taints, & PDB. Others?
-
Show this thread
-
Replying to @bgrant0607
awesome! definitely interested in your perspective on the tradeoffs picking a scheduling model, eg monolithic vs shared state. there‘s some stuff in the papers, but as k8s tends to gravitate back towards „kinda“ monolithic w/ sched framework what are learnings from borg?
2 replies 0 retweets 5 likes -
Replying to @embano1 @bgrant0607
in addition: borg seems to push out scheduling decision to borglets (from master), vs k8s is pull by watches by kubelet. what are the tradeoffs here, ie push vs pull at scale with failures, delays and conflicts?
1 reply 0 retweets 4 likes -
Replying to @embano1 @bgrant0607
and if i‘m totally wrong here, perhaps one more reason to explain this for dummies like me
1 reply 0 retweets 1 like
Originally K8s did push. See:http://issues.k8s.io/156
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.