In this article, we are going to see how we can disable docker support in k8s and add Containerd support in the live cluster.
If you are using Docker in Kubernetes cluster, then you need to move to another container platform.
Yes, you read it right!! We have to move to Containerd ( or similar technology) because Kubernetes removing support for docker.
Let's see why.
First of all, in simple layman's terms, Docker doesn't understand the language of Kubernetes. For that Docker uses Docker shim and Docker's whole stack, then it uses Containerd as its underlying CRI to create, delete, update containers.
Below are some comparisons between docker and Containerd.
In toml file enable cri plugin by commenting line, disabled_plugin = ["cri]".
Now, tell kubelet which container runtime you want to use, to do this we need to append some parameters (--container-runtime=remote --container-runtime-endpoint=unix:///run/containerd/containerd.sock) in "/var/lib/kubelet/kubeadm-flags.env" file.
After this, restart the Kubelet service.
Finally, we can uncordan the node using:"kubectl uncordan kworker1"., then we can see our runtime has been changed to Containerd.
We can do the same for all of our master and worker nodes.
Thank you for your time.
Comments
Post a Comment