From 8485b583a47c69182be5f4f392ba89e0757a9392 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Sch=C3=A4fer?= Date: Thu, 9 May 2019 01:45:52 +0200 Subject: [PATCH] Update docs, remove redundant instructions --- deployment/disaster-recovery/velero/README.md | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/deployment/disaster-recovery/velero/README.md b/deployment/disaster-recovery/velero/README.md index 9fa665d40..ce88860f8 100644 --- a/deployment/disaster-recovery/velero/README.md +++ b/deployment/disaster-recovery/velero/README.md @@ -20,23 +20,19 @@ download and extract e.g. [velero-v0.11.0-linux-arm64.tar.gz](https://github.com ## Setup Velero Namespace Follow their [getting started](https://heptio.github.io/velero/v0.11.0/get-started) -instructions to setup the Velero namespace: +instructions to setup the Velero namespace. We use +[Minio](https://docs.min.io/docs/deploy-minio-on-kubernetes) and +[restic](https://github.com/restic/restic), so check out Velero's instructions +how to setup [restic](https://heptio.github.io/velero/v0.11.0/restic): ```sh +# run from the extracted folder of the tarball $ kubectl apply -f config/common/00-prereqs.yaml $ kubectl apply -f config/minio/ ``` Once completed, you should see the namespace in your kubernetes dashboard. -We use [Minio](https://docs.min.io/docs/deploy-minio-on-kubernetes) and -[restic](https://github.com/restic/restic), so check out Velero's instructions -how to setup [restic](https://heptio.github.io/velero/v0.11.0/restic): - -```sh -$ kubectl apply -f config/minio/30-restic-daemonset.yaml -``` - ## Manually Create an On-Premise Backup When you create your deployments for Human Connection the required annotations