Closed Martin-Hogge closed 1 year ago
@Martin-Hogge please make sure you update your CRD's to the latest versions available for the v5.3.0
release.
For instance, as you can see in the latest version of the PGUpgrade
API, a value of 15
is supported for toPostgresVersion
:
toPostgresVersion:
description: The major version of PostgreSQL to be upgraded to.
maximum: 15
minimum: 10
type: integer
Ok my bad I didn't sync the fork beyfore upgrading pgo
. Thank you for your help !
For anybody stumbling upon this (with the upgrade to 16) and you need to update your CRDs in body should be less than or equal to 15
cd kustomize/install/crd/
kustomize build . | kubectl apply -f - --server-side --server-side
fthe upgrade from 5.4 to 5.5 i had to use
cd kustomize/install/crd/
kustomize build . | kubectl apply -f - --server-side --server-side --force-conflicts
actually, applying all the CRDS manually as an update will lead to issues when later applying the chart, since PGAdmin will then be already deployed.
Either delete the CRD for PGAdmin before you deploy or rather only update the old/existing CRDs like this
kubectl apply -f bases/postgres-operator.crunchydata.com_pgupgrades.yaml --server-side
kubectl apply -f bases/postgres-operator.crunchydata.com_postgresclusters.yaml --server-side --force-conflicts
I've had just upgraded my pgo cluster from
5.1.0
to5.3.0
and my postgresql version from13
to14
.I would like now to upgrade my postgresql version from
14
to15
as it should be supported by the latest version of pgo according to the release notes: https://access.crunchydata.com/documentation/postgres-operator/v5/releases/5.3.0/This is my
pgupgrade
yaml file:When I try to execute it I get the following message:
Here is my cluster:
My
pgo
deployment is usingregistry.developers.crunchydata.com/crunchydata/postgres-operator:ubi8-5.3.0-0
image.Is it a bug or should I configure something to be able to migrate from 14 to 15 ?
Thank you.