5.5.1 broken upgrade about postgres-operator HOT 2 CLOSED

hi @Elyytscha! Sorry to hear you are having trouble.

Unfortunately the v5.5.1 community OLM installers went out with a reference to an image (specifically for PG 14, as you're seeing) that doesn't exist in the Developer Registry. Per the Supported Platforms page within the CPK documentation, the latest two versions of Postgres are supported via the Crunchy Developer Program.

Additionally, I'll also reference the following GitHub issues for similar threads and conversations related to this:

• #3859 (comment)
• CrunchyData/postgres-operator-examples#255

Fortunately, you should be able to quickly get back up and running using the PG v14.10 and pgBackRest v2.47 images. This means you will need to update your PostgresCluster specs as follows (this is the Postgres version your cluster would have stayed at if the incorrect image reference hadn't been included in the OLM installer):

apiVersion: postgres-operator.crunchydata.com/v1beta1
kind: PostgresCluster
metadata:
  name: hippo
spec:
  backups:
    pgbackrest:
      image: registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.47-0
  image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.10-0
   ...

And from there you can perform a major PG upgrade to onto a supported version of PG using CPK's Major Postgres Version Upgrade functionality.

from postgres-operator.

thanks for the help, i will close

didn't noticed that only the latest 2 postgres version are supported

(it feels a little bit harsh to drop support in an upgrade from 5.5.0 -> 5.5.1 just saying)

my 2 cents

1. maybe support postgres 14 a little bit longer then usual until users had time to adapt https://www.crunchydata.com/blog/be-ready-public-schema-changes-in-postgres-15
2. support a convenient way to adapt 1 via postgrescluster custom resource, maybe

kind: PostgresCluster
apiVersion: postgres-operator.crunchydata.com/v1beta1
metadata:
  name: hippo
spec:
...
  defaultPublicAccess: true
  postgresVersion: 16
...

which defaults to no with the actual behaviour, while true gives the default user access to the public schema
(#3567 (comment))

from postgres-operator.