You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I was trying to set up PerconaXtraDBCluster with Cloudflare R2 bucket. They are one of the S3 compatible providers, but lack some APIs. Because of this, both xb-* and pitr pods are not working.
❯ k logs -f pxc-db-pitr-65b4c5d9d7-fftpf
Defaulted container "pitr" out of: pitr, pitr-init (init)
2025/01/10 02:15:56 run binlog collector
2025/01/10 02:15:58 Reading binlogs from pxc with hostname= pxc-db-pxc-0.pxc-db-pxc.pxc-db.svc.cluster.local
2025/01/10 02:15:58 Starting to process binlog with name binlog.000002
2025/01/10 02:15:58 ERROR: collect binlog files: manage binlog: put binlog.000002 object: put object binlog_1736460206_dc3e5ea63dad01f12979e81c74d24912: Header 'x-amz-checksum-algorithm' with value 'CRC32C' not implemented
Quick google search for Cloudflare R2 Header 'x-amz-checksum-algorithm' with value 'CRC32C' not implemented suggests that Cloudflare R2 and other providers don't support this API.
However, this error is specifically thrown with minio-go client which is used in this project. Example forum
I'm sure other S3 compatible providers like DigitalOcean and Google Cloud Storage etc suffer from the same problem. Would you consider swapping out minio client with official AWS S3 SDK or something similar? This would increase the adoption and compatibility of the operator.
Report
Hi. I was trying to set up
PerconaXtraDBCluster
with Cloudflare R2 bucket. They are one of the S3 compatible providers, but lack some APIs. Because of this, bothxb-*
andpitr
pods are not working.More about the problem
backup pod logs
pitr pod logs
Quick google search for
Cloudflare R2 Header 'x-amz-checksum-algorithm' with value 'CRC32C' not implemented
suggests that Cloudflare R2 and other providers don't support this API.However, this error is specifically thrown with minio-go client which is used in this project. Example forum
I'm sure other S3 compatible providers like DigitalOcean and Google Cloud Storage etc suffer from the same problem. Would you consider swapping out minio client with official AWS S3 SDK or something similar? This would increase the adoption and compatibility of the operator.
Steps to reproduce
PerconaXtraDBCluster
withVersions
Anything else?
No response
The text was updated successfully, but these errors were encountered: