Hello dear colleagues,
after reading the steps, I have configured containerd socket, applied, and tried the new configuration without docker - with 1.23.6, all was fine.
now I have upgraded to 1.24.0 and cannot start kubelet.
this is the configuration for the service:
/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--fail-swap-on=false --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamically
EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably, the user should use
# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.
#EnvironmentFile=-/etc/default/kubelet
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS
Cluster information:
Kubernetes version: 1.24.0
Cloud being used: vps
Installation method:
Host OS: ubuntu 20.04.4 LTS
CRI and version: containerd.io 1.6.4
please let me know what else needs to be changed.
perhaps I am missing something 
error:
May 12 21:33:41 server.. kubelet[82016]: --volume-stats-agg-period duration Specifies i>
May 12 21:33:41 server.. systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- The process' exit code is 'exited' and its exit status is 1.
May 12 21:33:41 server.. systemd[1]: kubelet.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
thank you
for those who has the same problem:
#remove
–network-plugin=cni
from: /var/lib/kubelet/kubeadm-flags.env