Bernard Grymonpon

Unable to use Azure Workload Identity for storage access for backups

1

### Report When using Azure Workload Identity (https://azure.github.io/azure-workload-identity/docs/introduction.html), no credentials or secrets are needed, as the pods are provided with a token in a well-known place, and the auth chain...

When installing through the latest published helm chart (which aligns with the helm chart contents found in the repo), you get a non-recent version (2.0.20-all). This also doesn't align with...

Haproxy keeps sending queries to non-ready nodes on shutdown

1

### Report Haproxy has a checkscript which is run every 10 seconds, and basically checks for non-maintenance mode, and a state of "4" (joined/synced). There is a situation where, with...

Backups no longer work after upgrading to 1.17.0

10

### Report After a operator and cluster upgrade towards 1.17.0 (crds + helm upgrade), backup jobs no longer complete (which worked fine in 1.16.1). The log for a backup is...

Backups can't be stored to a set prefix in a storage location

3

### Proposal Documentation states the following (at https://docs.percona.com/percona-operator-for-mysql/pxc/backup-tutorial.html#configure-backup-storage): > Also you can use the storages..s3.prefix option to specify the path (a sub-folder) to the backups inside the S3 bucket. If...

Error message for `aws s3 ls` refers to wrong endpoint.

4

### Describe the bug Given an s3 bucket in `eu-west-1`, when setting `AWS_REGION=eu-west-1` and `AWS_ENDPOINT_URL=https://s3.amazonaws.com` env vars and issuing an `aws s3 ls s3://bucketname/some/path/to/object`, it will give you the following...

Pitr collector can't handle transactions split over multiple binlogs

2

### Report (Operator: 1.18.0, PXC @@version: 8.0.42-33.1, Logcollector image: percona/percona-xtrabackup:8.0.35-33.1 with init image percona/percona-xtradb-cluster-operator:1.18.0.) When the set from the last uploaded binlog spans two binlogs on another host, the log...

Non-existing statefulsets are being deleted over and over

1

### Report I noticed that the percona mongodb operator fills my kube API logs with deletes of non-existant stateful sets every couple of seconds. This clutters the logs and spills...