Closed jbeda closed 7 years ago
any update on this issue? Thank you so much.
@overip The details are in https://github.com/kubernetes/release/issues/234 but you'll have to dig. I'm going to start pulling together some more consumable instructions now.
I'm collecting notes that are going to go in to the docs here: https://gist.github.com/jbeda/5e8a4ce0a23711da146e51900859c037
@jbeda Note that v1.5.5 of kubeadm probably can't deploy v1.5 clusters ;)
v1.6.0-alpha.0-2074+(somesha) is the stable v1.5 version of kubeadm
Yeah -- take a look a the gist and let me know what you think.
Ah, sorry commented without taking a look at the gist -- it looks good to me!
@jbeda it is great! Thank you so much!!!
Is there actually an issue with keeping older builds in the repository?
Why can't we have all the older versions in the repository along with the newer ones?
Indeed - It would just be so convenient, and yum would take the latest, and older version would only be taken if the complete NVR is given.
Happy to help with the createrepo calls if they are available somehwhere :)
@fabiand @rushabh268 -- @mikedanese is the guy that is driving this stuff and so he has the real story. But the nitty gritty details are in kubernetes/release#234.
Old versions for most components are in the repos. However, the version string for the previous kubeadm was, confusingly, 1.6.0-alpha. My understanding is that this caused problems when sorting with/against 1.6.0. Again, Mike has the details. For now I just want to get some solution documented.
This is a Feature Request
We have old versions in the various repositories now. The one exception is kubeadm due to the vagaries of how versions sorted. Yet the 1.5.5 version of kubeadm is available as a direct download. We should document this someplace.
See https://github.com/kubernetes/release/issues/234.