Gabriele Bartolini

I think we need to revisit the current documentation of the `pg_basebackup` recovery bootstrap, especially reducing the expectations in terms of migrations from other environments. There are so many things...

Why on earth did I link this ticket in that commit!?!?

@milas you are right. I was talking with @mnencia about this issue with `initdb` configuration. We'll keep you posted.

Normally, you should use a digest to pin a specific immutable version of the image, as outlined here: https://cloudnative-pg.io/documentation/current/quickstart/#part-3-deploy-a-postgresql-cluster Starting with 1.23 you have more flexibility with image catalogs. Regarding...

I am concerned about the introduction of this breaking change. Can we do something like what we did for the log field names? https://github.com/cloudnative-pg/cloudnative-pg/commit/936b930eaca7d0c85d571a7eac3fc6f401105551 And then get the plugin to...

Hi Philippe, > I'd suggest adding both for a while, there should be no issue in doing so and the cluster label would be overridden if needed. We can even...

oh ... and then we change the dashboard immediately and communicate the change. Got it. Thanks

Hi @wvengen, You are right. This is something that needs to be documented, at the very least. IMO, if you set the 'future' state (i.e. with), we should be able...

I was able to easily create a `k3d` cluster and deploy the operator. ``` $ ./hack/setup-cluster.sh -e k3d -r load deploy Creating k3d cluster pg-operator-e2e-v1-27-1 with version v1.27.1 INFO[0000] Prep:...

@BaudouinH is right. We can only delete WAL files when we delete a backup, and we delegate the operation to Barman Cloud for that (so there's little that can be...