Add S3 send_content_md5 config and default to use MD5 #5870
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does:
This PR adds a new config in S3 bucket client
send_content_md5
to specify the checksum algorithm to use when put objects. If true, use MD5. Otherwise use CRC32C.Previously, bucket client uses CRC32C, which got an issue reported in #5829 when using non Amazon S3 object storage like Cloudflare R2. With the change in this pr, it should work out of the box. Thanos sets this value to true by default as well
If users want to stick with using CRC32C, they can turn off this flag.
Which issue(s) this PR fixes:
Fixes #5829
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]