From bbef7a3e33f0d8d9ad5e948c09f557ec616bb11a Mon Sep 17 00:00:00 2001 From: Julia Evans Date: Wed, 4 Oct 2017 13:35:57 -0700 Subject: [PATCH] address comments Signed-off-by: Julia Evans --- docs/faq.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index cb4d7f782..d05c91270 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -2,12 +2,15 @@ ## When is it appropriate to use Ark instead of etcd's built in backup/restore? -If you only want to backup/restore a single etcd cluster, you're probably better off using etcd's -built in backup and restore tooling. +If you only want to backup/restore a single etcd cluster, you may be better of using etcd's backup +and restore tooling. However, doing so restricts you to reconstructing your Kubernetes cluster data +exactly as it was preserved. Etcd's restore tooling is good if what you want is to recover from +data loss in a single etcd cluster, but does not support more sophisticated restores such as cluster +migrations and restoring Kubernetes state stored across multiple etcd clusters. Ark is useful for: -* backing up etcd resources and persistent volume state +* backing up both Kubernetes resources and persistent volume state * cluster migrations * backing up a subset of your Kubernetes resources * backing up Kubernetes resources that are stored across multiple etcd clusters (for example if you @@ -16,5 +19,5 @@ Ark is useful for: ## Will Ark restore my Kubernetes resources exactly the way they were before? Yes, with some exceptions. For example, when Ark restores pods it deletes the `nodeName` from the -pod so that they can be scheduled onto a new node. You can see some more examples of the differences +pod so that it can be scheduled onto a new node. You can see some more examples of the differences in [pod_restorer.go](https://github.com/heptio/ark/blob/master/pkg/restore/restorers/pod_restorer.go)