We are not affected. We use kind for our end-to-end tests. Kind has moved away from the dockershim some time ago [1]. Cloudera internally has been running with containerd in their clusters for a long time also. We also run on Openshift, see the code ready containers documentation. OpenShift has not used the docker shim for even longer than kind [2].
We do not need to change our image build steps either. The docker containers we build still work. We do not need to remove docker from our build process. It only affects the container runtime nothing else. Supporting K8s v 1.24 is a different thing which we could look at for v1.0.0 if there is demand for it. Wilfred [1] https://kubernetes.io/blog/2022/02/17/dockershim-faq/#are-there-examples-of-folks-using-other-runtimes-in-production-today [2] https://www.redhat.com/en/blog/red-hat-openshift-container-platform-4-now-defaults-cri-o-underlying-container-engine#:~:text=With%20OpenShift%204%2C%20the%20default,and%20configuration%20of%20the%20cluster. On Wed, 16 Mar 2022 at 16:05, Weiwei Yang <[email protected]> wrote: > > Hi all > > During today's community meeting, the following issue has been raised by > Ryan. > As dockershim will be removed in K8s 1.24 ( > https://kubernetes.io/blog/2022/01/07/kubernetes-is-moving-on-from-dockershim/), > we need some assessment to see if we are affected. Such as > > - Do we have any issues supporting K8s 1.24? > - Do we need any changes in our build process to remove docker > dependency (e.g nerdctl <https://github.com/containerd/nerdctl>) > > BTW, we have quickly checked running YK on containerd runtime, it seems > everything is working fine. Please share your thoughts and spot potential > issues. > > Thank you. > Weiwei --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
