Cluster Scheduling Components Using containerd

In Kubernetes 1.20 and later versions, Docker cannot be used as the container runtime interface (CRI). In the production environment, if the Kubernetes of a later version is required, you need to choose another CRI. Cluster scheduling components are installed and verified based on the mainstream CRI containerd 1.4.4, and all components can run and function properly in the containerd + Kubernetes scenario.

For details about the containerd installation process, see the official document. During the installation of cluster scheduling components, Ascend Docker Runtime is used by default. You can configure containerd to use Ascend Docker Runtime instead of runc to automatically mount devices when the container is started. For details about how to configure containerd, see "Installing Ascend Docker Runtime in containerd Scenarios" in the Installation and Deployment section.