Gabriele Bartolini
Gabriele Bartolini
Closing this as it will be covered by #6292 and in the future by #7073
We have now moved to a different model and catalogs are in the artifacts project. Would this still be relevant?
I am closing this. I have added a new issue to keep track of that (#309).
Merged as part of #309 - thanks for the @solidDoWant. Please test this and let us know!
Can you please confirm that your Kubernetes cluster only has 3 nodes in total with two different architectures and you are asking to run a Postgres cluster on different architectures?
Oh, I love this feature!
I have tentatively set it to 1.28 - can be moved to 1.27 if we can sneak it there
In the review process we have decided to classify this as a bug and backport the fix to all supported versions of CloudNativePG: https://github.com/cloudnative-pg/cloudnative-pg/pull/7885#issuecomment-3051566945
Just trying to see if this can be added to the backlog for 1.24.2. Any news @NinoSkopac and @valeriodelsarto ? Thanks
I see you added only targetTime. Can you please ensure there's a way to add the other recovery targets specified in https://cloudnative-pg.io/documentation/current/recovery/#recovery-targets?