This message was deleted.
# k3s
This message was deleted.
For example, if you’re running version 1.25, ensure that you’re on the most recent patch version. Then, upgrade to the most recent patch version of 1.26.
The policy for all kubernetes distros is single steps between minor versions. no skipping minors.
🎯 2
🙏 1
I’ve actually been amateurishly not aware of this version skew policy and there I’ve bumped K3s based clusters several minor versions some times … it have went well … but okay this is duly noted
Ditto @late-needle-80860, i’ve jumped multiple minor versions on some of our test clusters…but good to know that we should stop that then 🙂
👍 1