LAB 4.1 Usage of CRI endpoints without URL scheme is deprecated

Hi @k0dard,

The --set option is one way to set the runtime and image endpoints. An alternate way is to create the /etc/crictl.yaml file.
I used the following command for the crictl.yaml file, based on the official crictl installation and usage documentation, and did not run into any usage errors:

$ sudo -c sh 'cat <<EOF > /etc/crictl.yaml
runtime-endpoint: unix:///run/containerd/containerd.sock
image-endpoint: unix:///run/containerd/containerd.sock
timeout: 2
debug: false
pull-image-on-create: false
EOF'

Regards,
-Chris

Hi @michael.weinrich,

Typically warnings can be disregarded and things should work as expected. However, after taking a closer look at the latest docs, it seems this config update may be expected by the kubeadm bootstrapping tool from its /var/lib/kubelet/kubeadm-flags.env config file. Try to update the value of --cri-socket in that file if needed, and try running the kubeadm upgrade plan command again.

Regards,
-Chris