This message was deleted.
# generala
adamant-kite-43734
09/26/2023, 7:03 PMThis message was deleted.
c
creamy-pencil-82913
09/26/2023, 7:37 PMeach RKE kubernetes release has a set of system images that it uses. If it is necessary to update an image in that set, without changing the actual Kubernetes version, the trailing digit is bumped to indicate a new release.
creamy-pencil-82913
09/26/2023, 7:38 PMThere are no backports or other changes compared to upstream. It’s just the way RKE represents the data for a release.
creamy-pencil-82913
09/26/2023, 7:38 PMf
flat-television-63609
09/26/2023, 7:57 PM@creamy-pencil-82913 thank you. So there would be no issue upgrading from
v1.19.6-rancher1-1v1.20.15-rancher2-2v1.21.14-rancher1-1c
creamy-pencil-82913
09/26/2023, 8:27 PMyou should generally speaking upgrade to the latest patch release of the current minor, and then to the latest patch release of the next minor, and so on until you’re up to date.
creamy-pencil-82913
09/26/2023, 8:28 PMI can’t say there are “no issues” because there are changes to component versions and kubernetes APIs between releases. You’d need to know your environment to know how an upgrade to a new minor would affect you.