minikube does not work with kubernetes 1.27 due to flag removal #16112
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
The kubelet can't start, because the --container-runtime=remote flag has been dropped:
"command failed" err="failed to parse kubelet flag: unknown flag: --container-runtime"
It is only needed for versions before 1.24, and has been deprecated in 1.24 through 1.26
https://kubernetes.io/blog/2023/03/17/upcoming-changes-in-kubernetes-v1-27/
There is also a similar change, that one now needs to add
unix://
before the CRI sockets.It is not needed to specify both endpoints, since the image endpoint will default to runtime:
But is mandatory to override them, since otherwise
kubeadm
will complain about the sockets.Found multiple CRI endpoints on the host. Please define which one do you wish to use by setting the 'criSocket' field in the kubeadm configuration file: unix:///var/run/containerd/containerd.sock, unix:///var/run/cri-dockerd.sock
Previously it would look for dockershim.sock before finding the containerd.sock (used by docker)
The text was updated successfully, but these errors were encountered: