This is an early umbrella task for deprecating and replacing Docker as a Container Runtime Engine for Wikimedia production kubernetes clusters
Per [1] with the release that is due for September 2021 (assuming that happens as planned), Docker will no longer be usable as a Container Runtime Engine for vanilla Kubernetes. And that's it. All other usages of Docker remain unchanged.
Given the support cycle of 12 months after a release is out, that gives us something less than 2 years for having evaluated the available replacements, settled on one, drafted and implemented a migration plan.
Below is the announcement in its entirety
Folks, If you haven't seen the discussions around $SUBJECT, please see [1] and [2]. Tl;dr Please evaluate and switch to CRI implementations that are or will be available in the community (like containerd, cri-o etc). For those who want to continue to use docker as their runtime, please see [3] and [4]. There will be changes to how you deploy/run your clusters as and when Mirantis/Docker folks come up with a migration plan for a separate (new!) external cri implementation. So watch that space. Issues, concerns, we can chat in sig-node slack channel or meetings (or drop a reply to this note). Thanks, Dims [1] https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/ [2] https://kubernetes.io/blog/2020/12/02/dockershim-faq/ [3] https://twitter.com/justincormack/status/1334976974083780609 [4] https://github.com/Mirantis/cri-dockerd -- Davanum Srinivas :: https://twitter.com/dims -- You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CANw6fcHRq%2BadjSkrt1dVQfFtcEc1sqtWRY7LktDFxKLt537Kkg%40mail.gmail.com.