This message was deleted.
# general
a
This message was deleted.
c
latest 2.5, than latest 2.6, then latest 2.7
s
Thanks! I'm giving it a go now
2.5.16 to 2.6.9
I really appreciate you answering this question for me. So far 2.5. to 2.6 has been fantastic. The new ui is a bit much at first to navigate, but Im slowly migrating legacy implementations of things to the new way. So far so good
m
@stocky-fall-82040 I too am in a similar boat as you were. I’m using vSphere as my infrastructure provider. Did you have any underlying issues jumping through all of those versions?
s
Ive upgraded from 2.5 to 2.6 without issues. The UI overhaul done in 2.6 has made it a lot more difficult to navigate. They replaced catalogs with repos, changed monitoring, logging and alerting. My current configuration is backwards compatible but im having to redeploy everything under the new way of doing things. Its a bit overwhelming
👍 1
m
I’m going to have to do that as well, as I use the “legacy” monitoring, alerting and logging bits, as well as storage classes for NFS and vSphere. 😞
I am wanting to get all of my RKE clusters on at least K8s v.1.20 first though.
s
Hey Jason, Just checking in to see how your migrations are going. I have Rancher 2.6.10 up and running. I've converted Catalogs to Repos and redeployed legacy apps with the new app deployment worklflow. I'm about to start logging conversion. I'm using RKE1 v1.24. I'm using Terraform Rancher2 provider to control the migrations.
m
Well not well. I’ve hit a blocker with our existing clusters not properly using the cloud provider storage class in Rancher 2.5 - so I can’t move on to 2.6. Newly provisioned clusters work fine, existing ones aren’t upgrading right.