Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
afbjorklund opened this issue Mar 21, 2023 · 0 comments · Fixed by #16124
Closed

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

afbjorklund opened this issue Mar 21, 2023 · 0 comments · Fixed by #16124
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.

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented Mar 21, 2023

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)

@afbjorklund afbjorklund added 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. labels Mar 21, 2023
@afbjorklund afbjorklund self-assigned this Mar 21, 2023
@afbjorklund afbjorklund removed their assignment Mar 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant