I've allowed one of my test clusters to upgrade to 1068.9.0 from 1010.6.0. After doing this, docker networking does not mesh up with the kubernetes networking layer. My pods get conflicting
172.17.0.0/24 IP addresses, preventing most of them from accessing any network resources (generally, either the first or last to start with any specific IP, depending on circumstances), instead of the customary Kubernetes
10.244.0.0/16 addresses.
Restarting Docker, the Kubelet, the Kube Proxy, and lastly deleting and rescheduling all pods will (usually) resolve the issue.
I've noticed the same issue with the 2 beta channel servers I mix-in to my production cluster, and have thus had to remove them from service.
Between these two releases, has something changed in Docker's start process in CoreOS? The Docker version has not been revved.