From fc01c33b0de6fcc3634cc88d1445922f80e3525a Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Fri, 24 Aug 2018 17:22:28 -0700 Subject: [PATCH] rancher up should be rke up --- content/rke/v0.1.x/en/etcd-snapshots/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rke/v0.1.x/en/etcd-snapshots/_index.md b/content/rke/v0.1.x/en/etcd-snapshots/_index.md index f9ab1d2bb6b..80b346fc933 100644 --- a/content/rke/v0.1.x/en/etcd-snapshots/_index.md +++ b/content/rke/v0.1.x/en/etcd-snapshots/_index.md @@ -158,7 +158,7 @@ To simulate the failure, let's power down `node2`. root@node2:~# poweroff ``` -Before restoring etcd and running `rancher up`, we need to retrieve the backup saved on S3 to a new node, e.g. `node3`. +Before restoring etcd and running `rke up`, we need to retrieve the backup saved on S3 to a new node, e.g. `node3`. | Name | IP | Role | @@ -205,7 +205,7 @@ After the new node is added to the `cluster.yml`, run `rke etcd snapshot-restore $ rke etcd snapshot-restore --name snapshot.db --config cluster.yml ``` -Finally, we need to restore the operations on the cluster by making the Kubernetes API point to the new `etcd` by running `rke up` again using the new `cluster.yml`. +Finally, we need to restore the operations on the cluster by making the Kubernetes API point to the new `etcd` by running `rke up` again using the new `cluster.yml`. ``` $ rke up --config cluster.yml