Cannot backup to other S3 providers (Backblaze) due to missing S3 options

[ToshY]

Report

The Percona operators are inconsistent in the way of S3 backup options. I've already encountered this problem for the XtraDB cluster, but the cr.yaml for this Postgres operator (and thus the values.yaml for the Helm chart) is also missing S3 backup options.

The percona-server-mongo-db also implements a lot more S3 options, which makes me wonder why this isn't applied to other operators.

More about the problem

Options that are missing and causing issues:

• forcePathStyle - bucketname part of path / https://github.com/percona/percona-helm-charts/pull/349
  • In https://github.com/percona/percona-postgresql-operator/pull/1034 this is renamed to uriStyle, which is inconsistent to official specs naming this forcePathStyle. Also inconsistent compared to percona-server-mongodb-operator.
• prefix - specific directory in bucket / https://github.com/percona/percona-helm-charts/issues/322 / https://github.com/percona/percona-xtradb-cluster-operator/issues/1991
• checksumAlgorithm - need to be disabled/empty for Backblaze / https://www.backblaze.com/docs/cloud-storage-s3-compatible-api#unsupported-features

Steps to reproduce

Versions

Anything else?

https://github.com/percona/percona-xtradb-cluster-operator/issues/2041