Updated IBM COS documentation

Added option checksumAlgorith, this stops 403 errors as per #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 <[email protected]>
vmware-tanzu · Aug 5, 2024 · dc38a2a · dc38a2a
1 parent d4e743b
commit dc38a2a
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 7 deletions.
diff --git a/changelogs/unreleased/8082-gjanders 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
@@ -65,8 +65,9 @@ velero install \
     --provider aws \
     --bucket <YOUR_BUCKET> \
     --secret-file ./credentials-velero \
+    --plugins velero/velero-plugin-for-aws:v1.10.0\
     --use-volume-snapshots=false \
-    --backup-location-config region=<YOUR_REGION>,s3ForcePathStyle="true",s3Url=<YOUR_URL_ACCESS_POINT>
+    --backup-location-config region=<YOUR_REGION>,s3ForcePathStyle="true",s3Url=<YOUR_URL_ACCESS_POINT>,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)