Rancher upgrade FAQ

This document (000020727) is provided subject to the disclaimer at the end of this document.

Situation

As we near the end of maintenance, end of life, and end of support for Rancher 2.5, we felt it pertinent to provide a one-stop FAQ page as customers begin to plan their upgrades.

All upgrades should go from the latest to the latest. For instance, if you are on 2.5.3, you should go to 2.5.latest and then to 2.6.latest. The stop on 2.5.latest should be about a week to ensure you can catch any issues before moving forward.

After the upgrade to 2.5.latest, you should then upgrade the underlying Kubernetes version to the latest supported version of the Rancher release. And again, the new Kubernetes version should be tested and verified for around one week. From there, progress to the next Rancher upgrade, test, and then Kubernetes.  

Many customers ask why we recommend one week. The 1-week recommendation is because this is often enough time for your clusters and app to be thoroughly tested and any issues flagged. We have seen customers who do less of a testing phase and only find issues when their cluster is being fully used and under normal "strain."

Here are some useful links for upgrades — see link (1) below for our team's general best practices around upgrade paths.
 
During the course of your upgrade, see link (2) for how you and your team can bump the severity of this case if there is an impacting event during your upgrade. Doing so will notify our on-call engineer, who will engage as quickly as possible.
 
Please review link (3) to verify that the Rancher and Kubernetes versions remain inline. It is best to ensure that any testing is done in a lower environment first so that you and your team can be more aware of any issues that the version jumps could have on your environment and applications.
 
Lastly, for our team to better understand the updated environment, would you please run our system support script (4). This script will give our team a better understanding of the upgraded environment and the ability to call out items that may be out of our best practices.

(1)https://www.suse.com/support/kb/doc/?id=000020061
(2)https://www.suse.com/support/kb/doc/?id=000020296
(3)https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/
(4)https://www.suse.com/support/kb/doc/?id=000020192

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000020727
  • Creation Date: 05-Oct-2022
  • Modified Date:05-Oct-2022
    • SUSE Rancher

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center