Docker is doing exactly what they should be, but in a manner that is destructive. Getting a built in consistent p2p routing mesh under every container is brilliant, and fixes one of the biggest problems with k8s and swarm (it's not really possible for these technologies to interoperate because of incompatibilities with the network model).
The big problem is the stability hit. 1.12 had no business loosing the rc label.
Why do you think this is a requirement of Google Cloud?
> If by google's age and experience, you mean the requirements of the Google Cloud
Quite on the contrary. Kubernetes flies in the face of Google's cloud APIs, and has to take advantage of every dirty trick it can. But it does that because the result is better. I can say that without hesitation, having worked on the logical conclusion of port-mapping (Borg).
> Getting a built in consistent p2p routing mesh under every container is brilliant, and fixes one of the biggest problems with k8s
That's hilarious to me, because what Docker calls "routing mesh" is a feature that Kubernetes has had since 1.0. It's different in some subtle ways, but again, for really important reasons.