bornav
bornav
This makes it completely unusable for my use case Reverting to v1.11.40, and freezing the automatic update till this is resolved
@xarinatan did you update the element client, same happened to me when I updated the client
@cormacrelf for me it's 2 stages, when first initializing the database, and then converting it to use as recovery a backup solution given this as a [reference](https://github.com/bornav/fluxcd/blob/main/kubernetes/apps/xauth/keycloak/new/pg-keycloak.yaml) when first setting...
@spietras in my case https://github.com/cloudnative-pg/cloudnative-pg/issues/5778#issuecomment-2782198691
> I think we've pretty much covered those questions in the discussion above. I would consider the issue resolved if someone wrote those findings up as documentation. yes and no,...
@titilambert Thanks for sharing but my personal opinion is that having to add additional dependency to the cluster to get expected behavior, does not seem like a solution, but a...
@tesshuflower I still have the cluster where this bug occurred untouched, i can test it as soon as it is merged
> because i had a hard time to figure out what my issue is (first time user here...) i came to the conclusion that i am affected by this as...
>Internally we didn't think the PR was actually a good idea as this would slow other replicationdestinations from completing Completely agree with the thinking behind it, since from what i...