I feel like I'm just not understanding the "docker approved" approach. Which is surprising because docker itself is so great.
The networking stuff seems interesting though, I'm very curious how the rest of the ecosystem will evolve to take advantage of it or not.
Brian Grant has explained it recently here: 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.
Me and a team are working on another open-source project, Convox, that offers this on AWS.
One differentiator is that we use "pure" AWS for everything.
Load balancing comes from configuring ECS and an ELB the right way. Logging is based on Kinesis and Lambda. We're seeing great reliability and manageability with this approach.