From 36d5d501f633fce360016bbaedd21f2474bce7e4 Mon Sep 17 00:00:00 2001 From: Julia Evans Date: Wed, 4 Oct 2017 14:04:00 -0700 Subject: [PATCH] reword again Signed-off-by: Julia Evans --- docs/faq.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index 3f8ff0c32..3577b3018 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -2,13 +2,11 @@ ## 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 may be better off 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. +Etcd's restore tooling is good for recovering from data loss in a single etcd cluster, but does not +support more sophisticated restores. If you only want to recover from data loss in a single etcd +cluster, you're likely better off using etcd's backup/restore tooling. -Ark is useful for: +Examples of cases where Ark is useful: * backing up both Kubernetes resources and persistent volume state * cluster migrations