Provide S3 plugin that aims to support any S3 compatible object storage.

[kaovilai]

Describe the problem/challenge you have

The MinIO Go Client SDK provides straightforward APIs to access any Amazon S3 compatible object storage.

The AWS SDK for GO v2 drop ListObject for ListObjectV2 among other "legacy APIs".
Some new headers were also added.

The bump to AWS SDK for GO v2 in aws plugin v1.9 broke many S3 Compatible Providers
as documented in vmware-tanzu/velero-plugin-for-aws#219

Cloud providers below are known to have issues with aws-sdk-go-v2 in some capacity.

Cloud Provider	Notes	Velero Issue	Cloud Provider Issue
Google Cloud Storage	Should use GCP plugin instead		https://issuetracker.google.com/issues/256641357
Net App	operation error S3: PutObject, https response error StatusCode: 501, RequestID: , HostID: , api error NotImplemented: The s3 command you requested is not implemented.	#7828 #8152	Fixed in ONTAP Release 9.15.1P2. Fixed in Net App StorageGRID® Version 11.8.0.7
Oracle		#8013
IBM COS	checksumAlgorithm="" should work if retention is not enabled	#7543
Hitachi Content Platform (HCP)
Cloudian		#8264
Qumulo	not compatible with x-id, etc.	#8312

Velero should try to provide an object store plugin using SDK that aims and has a history of providing/accepting patches for compatibility with multiple S3 Compatible Providers.

• Google Cloud Storage
• Hitachi
• Huawei EBS

If this plugin is to replace (don't have to) the current AWS-SDK-Go-V2 usage, the sdk should also implement AWS specifics like

• EKS Pod Identities
• AWS STS

and validates for specific features that only some s3 compatible providers support like virtual host endpoints

Minio Go SDK also support both ListObjectV1 and ListObjectV2 simultaneously.

Describe the solution you'd like

In the short term we can try to make v1.8 plugin work with all new velero versions until EOL of aws-sdk-go-v1 on July 31 2025
If there are changes to object store plugin struct, we can create v1.<latest-version>-sdk-v1 tag.

In the long term, if we can confirm that there are yet providers who are not compatible with aws-sdk-go-v2 in significant numbers or enough users do not want to upgrade their storage appliance software, then we will have to consider migrating or creating a new s3 compatible plugin.

Anything else you would like to add:

Environment:

• Velero version (use velero version):
• Kubernetes version (use kubectl version):
• Kubernetes installer & version:
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "The project would be better with this feature added"
• 👎 for "This feature will not enhance the project in a meaningful way"

aws-sdk-go-v2 issues:

• SignatureDoesNotMatch error when used with GCS aws/aws-sdk-go-v2#1816

[sseago]

I'm assuming that the 1.14.2/1.15 candidate part of this is "test with the existing 1.8 plugin" and the longer-term plan would be much later in coming.

[Lyndon-Li]

Does this problem happen to minio?

[kaovilai]

Minio is pretty up to date with everything (has ListObjectsV2), so I think not. But everyone else whose documentation only refer to aws-sdk-go-v1 as reference is unlikely to be updated on recently added APIs that are required by aws-sdk-go-v2.