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
-
-
Oh, I love this! Order slips for "message passing" and cooks/waitstaff as "nodes/processes/pods"

-
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).
End of conversation
New conversation -
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.