From 75210c7f4a5b93fbc119ccc6ac1b5b85c77c01fa Mon Sep 17 00:00:00 2001 From: Gareth Anderson Date: Mon, 5 Aug 2024 09:08:00 +0000 Subject: [PATCH] Re-adding this doc line as requested by @blackpiglet Signed-off-by: Gareth Anderson --- site/content/docs/main/contributions/ibm-config.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/site/content/docs/main/contributions/ibm-config.md b/site/content/docs/main/contributions/ibm-config.md index 8d53a2531..464f53c82 100644 --- a/site/content/docs/main/contributions/ibm-config.md +++ b/site/content/docs/main/contributions/ibm-config.md @@ -76,6 +76,12 @@ Additionally, you can specify `--use-node-agent` to enable [File System Backup][ (Optional) Specify [CPU and memory resource requests and limits][15] for the Velero/node-agent pods. +Once the installation is complete, remove the default `VolumeSnapshotLocation` that was created by `velero install`, since it's specific to AWS and won't work for IBM Cloud: + +```bash +kubectl -n velero delete volumesnapshotlocation.velero.io default +``` + For more complex installation needs, use either the Helm chart, or add `--dry-run -o yaml` options for generating the YAML representation for the installation. ## Installing the nginx example (optional)