From c0e105f5cd99bf596ed338eef3796622798cfaa9 Mon Sep 17 00:00:00 2001 From: Steve Kriss Date: Fri, 3 May 2019 11:38:14 -0600 Subject: [PATCH] add note about single credentials per provider to locations doc Signed-off-by: Steve Kriss --- docs/locations.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/locations.md b/docs/locations.md index 600ff8731..9da936595 100644 --- a/docs/locations.md +++ b/docs/locations.md @@ -18,6 +18,8 @@ This configuration design enables a number of different use cases, including: ## Limitations / Caveats +- Velero only supports a single set of credentials *per provider*. It's not yet possible to use different credentials for different locations, if they're for the same provider. + - Volume snapshots are still limited by where your provider allows you to create snapshots. For example, AWS and Azure do not allow you to create a volume snapshot in a different region than where the volume is. If you try to take an Velero backup using a volume snapshot location with a different region than where your cluster's volumes are, the backup will fail. - Each Velero backup has one `BackupStorageLocation`, and one `VolumeSnapshotLocation` per volume provider. It is not possible (yet) to send a single Velero backup to multiple backup storage locations simultaneously, or a single volume snapshot to multiple locations simultaneously. However, you can always set up multiple scheduled backups that differ only in the storage locations used if redundancy of backups across locations is important.