From c91f22c4743479fe05a984ff7dcc43c534101ba4 Mon Sep 17 00:00:00 2001 From: dkeightley <20566450+dkeightley@users.noreply.github.com> Date: Thu, 29 Sep 2022 21:28:06 +0000 Subject: [PATCH] Update docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md Co-authored-by: Billy Tat --- .../migrate-rancher-to-new-cluster.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md b/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md index 46dde4b28a8..97e3fc77c00 100644 --- a/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md +++ b/docs/how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/migrate-rancher-to-new-cluster.md @@ -127,6 +127,7 @@ Kubernetes v1.22, available as an experimental feature of v2.6.3, does not suppo 1. Apply the manifest, and monitor the Restore status: 1. Apply the `Restore` object resource: + ```bash kubectl apply -f restore-migration.yaml ```