This is very much Kubernetes's opinion, based on the production experience the engineers who built it. Brian Grant has explained it recently here: https://gith

This is very much Kubernetes's opinion, based on the production experience the engineers who built it. Brian Grant has explained it recently here: https://github.com/kubernetes/kubernetes/blob/master/docs/whatisk8s.md#kubernetes-is-not https://github.com/kubernetes/kubernetes/blob/master/docs/wh... "The technical definition of "orchestration" is execution of a defined workflow: do A, then B, then C. In contrast, Kubernetes is comprised of a set of control processes that continuously drive current state towards the provided desired state. It shouldn't matter how you get from A to C: make it so. This results in a system that is easier to use and more powerful, robust, and resilient." Look into PaaSes that are built on top of K8s, like Red Hat's OpenShift v3 or Deis.