-
Notifications
You must be signed in to change notification settings - Fork 715
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
kubeadm 1.5.6 package depends on kubelet 1.6.0 #213
Comments
Probably a bug in https://github.com/kubernetes/release/blob/master/debian/build.go, looking... |
I can't add the last stable version of kubeadm to the kubernetes repo because it's sort higher then 1.6.0 (it was 1.6.0-alpha). I think the right thing to do here is just remove old kubeadm versions. cc @luxas |
👎 to removing old versions. |
Kubeadm is alpha in 1.5. My concern is that we have absolutely no idea whether kubeadm 1.5.6 works with the rest of 1.5.6 because we haven't tested this configuration ever. |
I see. It seems the problem I have now with kubeadm 1.6 is kubernetes/kubernetes#43815 . But because I can't even install any other kubeadm version it means I can't use kubeadm at all. |
If you want, you can use kubernetes-xenial-unstable which has the fixed kubeadm packages. I'm very hesitant to tag an untested alpha release as stable when a beta exists. https://packages.cloud.google.com/apt/dists/kubernetes-xenial-unstable/main/binary-amd64/Packages |
I will let @luxas weigh in. |
I'm leaving 1.5.6 in stable until 1.6 isn't broken. I'm going to remove it after since it's alpha with known vulnerabilities and not tested. After 1.6, we will leave the debs in the repo forever. |
Thanks! |
BUG REPORT
What happened?
https://packages.cloud.google.com/apt/dists/kubernetes-xenial/main/binary-amd64/Packages currently has this definition for kubeadm 1.5.6:
So I can't install kubeadm with kubernetes 1.5.x
How to reproduce it (as minimally and precisely as possible)?
$ sudo apt-get install -y kubelet=1.5.6-00 kubeadm=1.5.6-00 kubectl=1.5.6-00 kubernetes-cni
output:
The text was updated successfully, but these errors were encountered: