From 86adb6c102574d8d3981e8ff848d037c9deaf78a Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Fri, 22 Nov 2019 09:52:47 -0700 Subject: [PATCH] Making the same change to the other tab --- .../latest/en/etcd-snapshots/restoring-from-backup/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 32f983ea64e..a4e0ce38419 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 @@ -73,9 +73,9 @@ $ rke etcd snapshot-restore \ {{% /tab %}} {{% tab "RKE prior to 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 etcd to a specific snapshot. +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 are included in `rke etcd snapshot-restore`: +The following actions will be performed when you run the command: - Removes the old etcd cluster - Rebuilds the etcd cluster using the local snapshot