Kubernetes doesn’t “orchestrate”. It choreographs. Orchestration implies a static, procedural script with a start & end; not how k8s works.
Choreography more accurately distills what k8s does: improvisational evolution of dynamically controlled processes. h/t @bgrant0607 @jbeda
-
Show this thread
-
Joe has called this "jazz improv". There's no perfect analogy. I was thinking a short-order kitchen with multiple cooks and multiple waitstaff might be a better analogy. Each person has bounded responsibility and knows their role, and they communicate via order slips. :-)
1 reply 1 retweet 9 likes -
Replying to @bgrant0607 @jbeda
Oh, I love this! Order slips for "message passing" and cooks/waitstaff as "nodes/processes/pods"
1 reply 0 retweets 2 likes
Usually the order slips are tacked up onto some bar (etcd) that both the cooks and wait staff can access. The requests aren't totally ordered. Any state updates (scratching off items) are made to those slips. They are removed when the plate is delivered (termination).
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.