From dc38a2a879cd625bfc3e8f17b6a5d11f0df69dbc Mon Sep 17 00:00:00 2001 From: Gareth Anderson Date: Mon, 5 Aug 2024 04:16:34 +0000 Subject: [PATCH 1/2] Updated IBM COS documentation Added option checksumAlgorith, this stops 403 errors as per https://github.com/vmware-tanzu/velero/issues/7543 Added plugins line as velero install failed without this option in version 1.14.0 Removed the volumesnapshotlocation as it does not exist in 1.14.0 Signed-off-by: Gareth Anderson --- changelogs/unreleased/8082-gjanders | 1 + site/content/docs/main/contributions/ibm-config.md | 9 ++------- 2 files changed, 3 insertions(+), 7 deletions(-) create mode 100644 changelogs/unreleased/8082-gjanders diff --git a/changelogs/unreleased/8082-gjanders b/changelogs/unreleased/8082-gjanders new file mode 100644 index 0000000000..3b5327464a --- /dev/null +++ b/changelogs/unreleased/8082-gjanders @@ -0,0 +1 @@ +Updates to IBM COS documentation to match current version diff --git a/site/content/docs/main/contributions/ibm-config.md b/site/content/docs/main/contributions/ibm-config.md index 332d0a5701..8d53a2531c 100644 --- a/site/content/docs/main/contributions/ibm-config.md +++ b/site/content/docs/main/contributions/ibm-config.md @@ -65,8 +65,9 @@ velero install \ --provider aws \ --bucket \ --secret-file ./credentials-velero \ + --plugins velero/velero-plugin-for-aws:v1.10.0\ --use-volume-snapshots=false \ - --backup-location-config region=,s3ForcePathStyle="true",s3Url= + --backup-location-config region=,s3ForcePathStyle="true",s3Url=,checksumAlgorithm="" ``` Velero does not have a volume snapshot plugin for IBM Cloud, so creating volume snapshots is disabled. @@ -75,12 +76,6 @@ 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) From 75210c7f4a5b93fbc119ccc6ac1b5b85c77c01fa Mon Sep 17 00:00:00 2001 From: Gareth Anderson Date: Mon, 5 Aug 2024 09:08:00 +0000 Subject: [PATCH 2/2] 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 8d53a2531c..464f53c826 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)