mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-09 22:47:27 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

address comments

Browse Source 
Signed-off-by: Julia Evans <julia@stripe.com>
This commit is contained in:
Julia Evans
2017-10-04 13:35:57 -07:00
parent 62b32dad1d
commit bbef7a3e33
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/faq.md
View File

@@ -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)