doc: fix restore operator walkthrough
@@ -20,6 +20,21 @@ Note that currently the etcd-restore-operator only supports restoring from backu
>Note: This demo uses the `default` namespace.
+
+### Simulate disaster failure
+
+1. Make sure `example-etcd-cluster` EtcdCluster CR exists
+
+ ```sh
+ kubectl get etcdcluster example-etcd-cluster
+ ```
+
+2. Kill etcd pods to simulate disaster failure
+
+ ```sh
+ kubectl delete pod -l app=etcd,etcd_cluster=example-etcd-cluster --force --grace-period=0
+ ```
+
### Deploy the etcd-restore-operator
1. Create a deployment of the etcd-restore-operator:
@@ -91,7 +106,7 @@ sed -e 's|<full-s3-path>|mybucket/etcd.backup|g' \
1. Check the `status` section of the `EtcdRestore` CR:
```sh
- $ kubectl get etcdrestore restored-etcd-cluster -o yaml
+ $ kubectl get etcdrestore example-etcd-cluster -o yaml
apiVersion: etcd.database.coreos.com/v1beta2
kind: EtcdRestore
...
@@ -104,7 +119,7 @@ sed -e 's|<full-s3-path>|mybucket/etcd.backup|g' \
```
$ kubectl get etcdcluster
NAME KIND
- restored-etcd-cluster EtcdCluster.v1beta2.etcd.database.coreos.com
+ example-etcd-cluster EtcdCluster.v1beta2.etcd.database.coreos.com
```
3. Verify that the etcd-operator scales the cluster to the desired size:
@@ -114,9 +129,9 @@ sed -e 's|<full-s3-path>|mybucket/etcd.backup|g' \
NAME READY STATUS RESTARTS AGE
etcd-operator-2486363115-ltc17 1/1 Running 0 1h
etcd-restore-operator-4203122180-npn3g 1/1 Running 0 30m
- restored-etcd-cluster-0000 1/1 Running 0 8m
- restored-etcd-cluster-0001 1/1 Running 0 8m
- restored-etcd-cluster-0002 1/1 Running 0 8m
+ example-etcd-cluster-0000 1/1 Running 0 8m
+ example-etcd-cluster-0001 1/1 Running 0 8m
+ example-etcd-cluster-0002 1/1 Running 0 8m
```
### Cleanup
@@ -125,7 +140,7 @@ Delete the etcd-restore-operator deployment and service, and the `EtcdRestore` C
>Note: Deleting the `EtcdRestore` CR won't delete the `EtcdCluster` CR.
```sh
-kubectl delete etcdrestore restored-etcd-cluster
+kubectl delete etcdrestore example-etcd-cluster
kubect delete -f example/etcd-restore-operator/deployment.yaml
```
