public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-23 05:15:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update rollbacks.md (#698)

Browse Source 
* Update rollbacks.md

Removed step to scale Rancher down as cannot create the restore resource via the UI if rancher is scaled down and the Restore will scale Rancher to 0 when it starts

* Update rollbacks.md

Removed step to scale Rancher down as cannot create the restore resource via the UI if rancher is scaled down and the Restore will scale Rancher to 0 when it starts

* Update rollbacks.md

Removed step to scale Rancher down as cannot create the restore resource via the UI if rancher is scaled down and the Restore will scale Rancher to 0 when it starts

* Update rollbacks.md

Removed step to scale Rancher down as cannot create the restore resource via the UI if rancher is scaled down and the Restore will scale Rancher to 0 when it starts
This commit is contained in:
Tony Hansen
2023-06-28 12:18:06 -05:00
committed by GitHub
parent 56ca7d14f3
commit fbfaf54bc4
4 changed files with 0 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/rollbacks.md
-9
View File
@@ -23,15 +23,6 @@ A restore is performed by creating a Restore custom resource.
> * Follow the instructions from this page for restoring rancher on the same cluster where it was backed up from. In order to migrate rancher to a new cluster, follow the steps to [migrate rancher.](../../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md)
> * While restoring Rancher on the same setup, the Rancher deployment is manually scaled down before the restore starts, then the operator will scale it back up once the restore completes. As a result, Rancher and its UI will be unavailable until the restore is complete. While the UI is unavailable, use the original cluster kubeconfig with the restore YAML file: `kubectl create -f restore.yaml`.
### Scale the Rancher Deployment to 0
1. From the **Global** view, hover over the **local** cluster.
1. Under **Projects in local**, click on **System**.
1. From the **cattle-system** namespace section, find the `rancher` deployment.
1. Select **⋮ > Edit**.
1. Change **Scalable deployment of _ pods** to `0`.
1. Scroll to the bottom and click **Save**.
### Create the Restore Custom Resource
1. In the **Cluster Explorer,** go to the dropdown menu in the upper left corner and click **Rancher Backups.**