Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
kubeadm init specifying a version may result in a kubelet version mismatch #53832
Is this a BUG REPORT or FEATURE REQUEST?:
The upshot of that is that you can end up with kubeadm, kubectl and kubelet versions that are (potentially much) newer than the kube containers that kubeadm runs based on the --kubernetes-version option.
This hasn't caused any noticeable issues in the past, but with the advent of 1.8 we started to notice that iSCSI mounts were suddenly failing. However, if we downgrade kubelet to match the version of Kubernetes we installed, it works fine.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
If you create an iSCSI PV after that and try to consume it from a pod, the kubelet will fail to mount it. If you then downgrade kubelet to 1.7.8, the mount succeeds.
Anything else we need to know?:
@luxas @liggitt To avoid this, shall we let