https://rancher.com/ logo
Title
a

able-salesclerk-52921

04/05/2023, 5:02 PM
can a rancher 2.5 cluster be upgraded straight to 2.7.1? or do i need to go from 2.5-2.6-2.7?
b

bulky-sunset-52084

04/05/2023, 5:43 PM
you should move one version at a time - you should also make sure you follow the support matrix to assure ALL of the software around Rancher (such as the OS, Docker and K8s). Is supported on the versions you are jumping too. you might have to play a game of leap frog to get to the latest version. (honestly - at a certain point its easier to just start over)
a

able-salesclerk-52921

04/05/2023, 6:09 PM
starting over is probably not really going to be feasible
we have 2 legacy clusters that are 1.18, i know it's below the lowest certified version, but would it break if we upgrade to 2.6/2.7?
b

bulky-sunset-52084

04/05/2023, 6:15 PM
I cant say for certain but probably. 2.6 nor 2.7 have been certified with anything that old
It won't break the clusters - but rancher won't work quite right
a

able-salesclerk-52921

04/05/2023, 6:16 PM
they're legacy clusters we're moving workloads off them
b

bulky-sunset-52084

04/05/2023, 6:16 PM
This is why we STRONGLY advise following the support matrix. It's what we test to work
a

able-salesclerk-52921

04/05/2023, 6:17 PM
in what way do you mean "won't work quite right"? we won't be making any changes to those clusters and they will be replaced with new ones within supported version range, we just need them to be connected to rancher in the meantime
b

bulky-sunset-52084

04/05/2023, 6:21 PM
Rancher talks to clusters via the kubernetes API if the kubernetes API is too old there are likely to be communication and control issues with rancher and it's agents on the downstream clusters. I have no idea what exact issues you will face or if you will even face any... But that's the point - it's not tested so no one does. You're breaking ground testing for us essentially.
a

able-salesclerk-52921

04/05/2023, 6:38 PM
i see