search

vmware-tanzu / velero

Backup and migrate Kubernetes applications and their persistent volumes
https://velero.io
Apache License 2.0
8.53k stars 1.38k forks source link

velero backup create fails to upload backup to s3 using aws plugin #7543

Open Wayne-H-Ha opened 5 months ago

Wayne-H-Ha commented 5 months ago

Discussed in https://github.com/vmware-tanzu/velero/discussions/7542

Originally posted by **Wayne-H-Ha** March 19, 2024 We used to be able to create backup using velero 1.12.2 and aws plugin 1.8.2. We tried velero 1.13.0 and plugin 1.9.0 and it failed so we switched back to older version. We tried again with velero 1.13.1 and plugin 1.9.1 and it still fails. Any configuration change we need to make in order to use the new version? We tried to find the backup in s3 and it didn't get uploaded there. When we describe the backup, it returns: ``` velero-v1.13.1-linux-amd64/velero describe backup cp-20240319163110 | tail Started: 2024-03-19 16:32:01 +0000 UTC Completed: Expiration: 2024-04-18 16:32:01 +0000 UTC Total items to be backed up: 2871 Items backed up: 2871 Backup Volumes: ``` We believe the problem is a suffix "@aws" is added to key id? For example, aws_access_key_id = "3..0" but "3..0@aws" is passed to s3? Is there a configuration we can use to not having this suffix added? ``` cat /credentials/cloud [default] aws_access_key_id = "3..0" aws_secret_access_key = "a..b" ```
Wayne-H-Ha commented 1 month ago

IBM COS said they are working on implementing sdkv2 support in their product.