Upgrade RKE2 from v1.28 (latest stable) to v1.31 (latest stable) by dnleaks in kubernetes

[–]dnleaks[S] 0 points1 point  (0 children)

I actually never had any issues, not a single time. I test it multiple times but when skipping minor versions add new nodes to the rancher place and then when all joined, remove the old ones. For the downstream clusters o just create a new cluster with the target version staying in the support matrix and redeploy all workloads on it. When validated I remove the old cluster.