Question

You are provisioning a new control-plane node with kubeadm. The node has both containerd (socket at unix:///run/containerd/containerd.sock) and CRI-O (socket at unix:///run/crio/crio.sock) installed. When you run 'kubeadm init', the command fails with an error indicating that multiple container runtime endpoints were detected and it cannot proceed. You want the cluster to use containerd. Which action correctly resolves this and initializes the cluster?

Accepted Answer

Run 'kubeadm init --cri-socket unix:///run/containerd/containerd.sock' to explicitly select the containerd runtime endpoint.

Answer

Set the KUBELET_EXTRA_ARGS environment variable to point to containerd and re-run 'kubeadm init' without additional flags.

Answer

Uninstall the kubelet, reinstall it, and run 'kubeadm init', which auto-detects the first runtime alphabetically.

Answer

Run 'kubeadm init --container-runtime=containerd' since kubeadm reads the runtime name directly.