This message was deleted.
# k3sa
adamant-kite-43734
07/15/2024, 5:28 PMThis message was deleted.
c
creamy-pencil-82913
07/15/2024, 6:17 PMyou don’t have to, but it is a good idea to always be on the latest patch release of your current minor, before going to the next minor.
creamy-pencil-82913
07/15/2024, 6:18 PMThis is a Kubernetes thing: https://kubernetes.io/releases/version-skew-policy/#supported-component-upgrade-order
the Kubernetes project recommends that you do the following to benefit from as many regression and bug fixes as possible during your upgrade:
• Ensure that components are on the most recent patch version of your current minor version.
• Upgrade components to the most recent patch version of the target minor version.
For example, if you’re running version 1.29, ensure that you’re on the most recent patch version. Then, upgrade to the most recent patch version of 1.30.
a
abundant-hair-58573
07/15/2024, 6:22 PMOk cool thanks, I did see that when upgrading RKE2 the other day, I guess it makes sense it also applies to K3s. Just trying to avoid making unnecessary import requests into our air-gapped network
4 Views