From 6e408a1165d342af543cb9d6f366e59c8cabc02d Mon Sep 17 00:00:00 2001 From: Tejeev Date: Fri, 22 Nov 2019 12:28:36 +0000 Subject: [PATCH] Clarification --- .../latest/en/etcd-snapshots/restoring-from-backup/_index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/rke/latest/en/etcd-snapshots/restoring-from-backup/_index.md b/content/rke/latest/en/etcd-snapshots/restoring-from-backup/_index.md index c6dae0f85fc..32f983ea64e 100644 --- a/content/rke/latest/en/etcd-snapshots/restoring-from-backup/_index.md +++ b/content/rke/latest/en/etcd-snapshots/restoring-from-backup/_index.md @@ -8,7 +8,9 @@ The details of restoring your cluster from backup are different depending on you {{% tabs %}} {{% tab "RKE v0.2.0+"%}} -If there is a disaster with your Kubernetes cluster, you can use `rke etcd snapshot-restore` to recover your etcd. This command reverts the etcd to a specific snapshot. The following actions are included in the command: +If there is a disaster with your Kubernetes cluster, you can use `rke etcd snapshot-restore` to recover your etcd. This command reverts etcd to a specific snapshot and should be run on an etcd node of the the specific cluster that has suffered the disaster. + +The following actions will be performed when you run the command: - Syncs the snapshot or downloads the snapshot from S3, if necessary. - Checks snapshot checksum across etcd nodes to make sure they are identical.