tjmoore4

@benjamin-bergia Thank you for the use case details; I've added them to our feature backlog.

Closing this issue. Please reopen if you are still encountering this problem and would like further assistance.

@Schmaetz Thank you for the additional information. As mentioned above, PR #3106 shortened the generated scheduled backup CronJob names by removing `pgbackrest-`. This should allow for reasonable PostgresCluster names and...

@todeb that is the expected behavior. At this time, DB connection information is only auto-populated when using usernames & passwords with pgAdmin4, not when using using the LDAP integration. Any...

Closing this issue. Please re-open if you require further assistance.

@darktempla In case you missed it, Crunchy PGO 5.2.0 is now available on OperatorHub.

@maxsivkov Affinity for backup Jobs has been added with #3260, so closing this issue.

Since this issue involves functionality from an older version of Crunchy Postgres for Kubernetes, I am proceeding with closing this issue. If you have any additional questions - or if...

@Zvezdoreel We are planning to release that version as well, but are currently encountering some issues deploying our installers via the Red Hat certification process. We are actively working with...

@David-Angel I did some testing for this scenario as well and wasn't able to replicate your error scenario either. It might be helpful to have the `describe` output from any...