From 31b8ff92dfccbb02746cb771a7312e43e4b6bc4d Mon Sep 17 00:00:00 2001 From: Steve Kriss Date: Thu, 28 Jun 2018 13:40:02 -0700 Subject: [PATCH] add FAQ about using a bucket per cluster Signed-off-by: Steve Kriss --- docs/faq.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/faq.md b/docs/faq.md index fec16d8d7..b8912bdf9 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -23,3 +23,16 @@ Examples of cases where Ark is useful: Yes, with some exceptions. For example, when Ark restores pods it deletes the `nodeName` from the pod so that it can be scheduled onto a new node. You can see some more examples of the differences in [pod_action.go](https://github.com/heptio/ark/blob/master/pkg/restore/pod_action.go) + +## I'm using Ark in multiple clusters. Should I use the same bucket to store all of my backups? + +We **strongly** recommend that you use a separate bucket per cluster to store backups. Sharing a bucket +across multiple Ark instances can lead to numerous problems - failed backups, overwritten backups, +inadvertently deleted backups, etc., all of which can be avoided by using a separate bucket per Ark +instance. + +Related to this, if you need to restore a backup from cluster A into cluster B, please use [restore-only][1] +mode in cluster B's Ark instance while it's configured to use cluster A's bucket. This will ensure no +new backups are created, and no existing backups are deleted or overwritten. + +[1]: config-definition.md#main-config-parameters \ No newline at end of file