添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接

minikube does not work with kubernetes 1.27 due to flag removal #16112

Closed
@afbjorklund

Description

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.

I0321 11:21:01.182927   11125 util_unix.go:103] "Using this endpoint is deprecated, please consider using full URL format" endpoint="/var/run/cri-dockerd.sock" URL="unix:///var/run/cri-dockerd.sock"
I0321 11:21:01.197552   11125 util_unix.go:103] "Using this endpoint is deprecated, please consider using full URL format" endpoint="/var/run/cri-dockerd.sock" URL="unix:///var/run/cri-dockerd.sock"

It is not needed to specify both endpoints, since the image endpoint will default to runtime:

runtime-endpoint: unix:///var/run/cri-dockerd.sock
image-endpoint: unix:///var/run/cri-dockerd.sock

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)