You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since kubeadm is still not a production ready tool, it would be great if we could go back to a kubeadm version which we know to work for us. When something like #212 happens, downgrading is very useful.
In kubevirt, we use kubeadm, to deploy kubernetes on our vagrant development- and CI-environment and it works great. I like using the latest version, and so also help finding possible new issues, but having the possibility to downgrade until something blocking is resolved, would be cool.
As far as I have seen, the old versions are still on the storage, they are just not referenced anymore. Could that be? We are using the CentoOS repo mentioned in the kubeadm getting started guide.
The text was updated successfully, but these errors were encountered:
Since kubeadm is still not a production ready tool, it would be great if we could go back to a kubeadm version which we know to work for us. When something like #212 happens, downgrading is very useful.
In kubevirt, we use kubeadm, to deploy kubernetes on our vagrant development- and CI-environment and it works great. I like using the latest version, and so also help finding possible new issues, but having the possibility to downgrade until something blocking is resolved, would be cool.
As far as I have seen, the old versions are still on the storage, they are just not referenced anymore. Could that be? We are using the CentoOS repo mentioned in the kubeadm getting started guide.
The text was updated successfully, but these errors were encountered: