Bernard Grymonpon

> > Belgian data for today is in the correct format. So maybe it is fixed. If prices of tomorrow break it again I will look into merging the patch...

The issue I had was that the values are set by some external tooling/scripting for taking backups. Their logic (see https://github.com/percona/percona-docker/blob/main/percona-xtradb-cluster-8.4-backup/lib/pxc/aws.sh#L6-L7) was to set the default value of `https://s3.amazonaws.com` if...

I assume you'd only need the backup part (i've left out the pxc en haproxy sections). We use the helm chart for DB deployment (from https://github.com/percona/percona-helm-charts/tree/main/charts/pxc-db). This is the terraform...

This results in a different error, indicating that I should be using the correct endpoint. I double checked, the bucket is in the `eu-west-1` region. ``` xb-endpoint-test-backup-xvqc9 xtrabackup + LIB_PATH=/usr/lib/pxc...

After some debugging, I must conclude that I've hit two bugs: - the error the AWS-CLI throws when not setting the endpoint includes the text "Please send all future requests...

(fyi, https://github.com/aws/aws-cli/issues/9479 has the report for aws-cli.)

I'd suggest to leave the endpoint-construction op to the AWS CLI code, as they own the logic to it. Replicating that logic might lead to other things not working ......

> We are also encountering this issue, is there some workaround for the time being, or is it safe to downgrade the operator? 🤔 I currently solved it by setting...

how would the peer-list influence the S3 endpoint used for the storage of a backup?

Hitting the same issue here. For completeness, a `kubectl delete node xxx` on either GCP or Azure will actually terminate the backing VM as well, allowing for complete node management...