Page History

...

• https://github.com/docker/docker/pull/18108 (closed) "don't try to use default route MTU as container MTU"
  • "Trying to use the default route's MTU as the container (bridge) MTU is a bad idea:..."
• https://github.com/docker/docker/issues/22028 (closed) "docker 1.10, 1.11 do not infer MTU from eth0; docker 1.9 does" 
  • "this was a deliberate change, and specifying the MTU is the solution for this"
• https://github.com/docker/docker/issues/22297 (closed) "containers in docker 1.11 does not get same MTU as host" 
  • "In another PR (#18108) it was decided to drop the behavior where the mtu for the containers running on the default bridge network would be inherited from the host (there were valid concerns with that approach and @phemmer IIRC lead the discussion)"

Conclusion

• Not much we care about in the engine, but there is more stability in 1.11.
• Docker 1.11.2 should not be a problem, but we need to test it. 
• Need to resolve DinD API version problem if we upgrade

...

• We should be able to test the new ansible with Kubernetes 1.4.5 without changing much of our beta deployment process, which is a good thing.
• David:
  • To get SDSC up we need newer ansible, we need to move our ansible forward, if we're using contrib we might need to forward that as well.
  • Pulled new kubernetes contrib ansible and it seems forward compatible
• Other options: (most of what we need is to provision openstack)
  • kubeadm
  • ket: https://github.com/apprenda/kismatic

Kubernetes

1.3 http://blog.kubernetes.io/2016/07/kubernetes-1.3-bridging-cloud-native-and-enterprise-workloads.html

...