How to rollback the Kubernetes version of a Rancher v2.x provisioned cluster
This document (000020195) is provided subject to the disclaimer at the end of this document.
This article details how to rollback the Kubernetes version of a Rancher v2.x provisioned cluster.
A Kubernetes Cluster Rollback will most definitely cause downtime in the cluster, as you are restoring a snapshot from before the upgrade and the cluster will have to reconcile state.
- In order to rollback your Kubernetes cluster version upgrade, you need to have first taken an etcd snapshot from before the upgrade. You should keep the reference to the snapshot name that was created as your "pre-upgrade" snapshot. In my cluster which has cluster ID:
c-q8st7, my snapshot name was
c-q8st7-ml-qdxdh. Our example upgrade is from
In order to rollback, you must:
- Edit Cluster
- Edit as YAML
v1.14.9-rancher1-2(or whatever your desired restore version is)
restorekey in the YAML.
You will need to update the following configuration:
rancher_kubernetes_engine_config: restore: restore: false
You'll want to closely model the following:
rancher_kubernetes_engine_config: restore: restore: true snapshot_name: "c-q8st7:c-q8st7-ml-qdxdh"
snapshot_namehas the cluster ID prefixed to it with a
Finally, you can save the cluster, and observe the snapshot restore + K8s version rollback occur.
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:000020195
- Creation Date: 06-May-2021
- Modified Date:06-May-2021
- SUSE Rancher
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com