postgres_14 image is not available

[budimanjojo]

The registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.11-0 is not available in the registry although being the default value of postgres_14.

[neoighodaro]

This totally broke our prod kubernetes cluster.

[bap-dev]

same here!
CrunchyData/postgres-operator#3859

[neoighodaro]

it would seem it was removed.

[bap-dev]

btw. the whole registry seems to not be availible anymore:
CrunchyData/postgres-operator#3601

[budimanjojo]

They shouldn't bump the postgres_14 in the values.yaml file if they're not gonna update the image anymore. Such a weird decision. They should either just keep the value the same or just remove the entire postgres_14 and notify the users.

[neoighodaro]

They shouldn't bump the postgres_14 in the values.yaml file if they're not gonna update the image anymore. Such a weird decision. They should either just keep the value the same or just remove the entire postgres_14 and notify the users.

Do you know a quick fix? I am trying to avoid even upgrading at this point as its too quick a response, but since prod is down, this may be the only option.

[budimanjojo]

@neoighodaro you can just put something like this in your values.yaml file:

relatedImages:
  postgres_14:
    image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.10-0

[bap-dev]

same thing: curl -L https://registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.10-0
{ "errors":[{"code":"404","message":"This container version is no longer available from the Crunchy Data Developer Program. For information on accessing these containers, please contact info@crunchydata.com." }]

[budimanjojo]

It's still working in my environment though. Curling all images returns the same error as above, but I can pull the image:

docker pull registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.10-0

[bap-dev]

yeah, I can confirm this. 14.10-0 is working 14.11-0 not!

[neoighodaro]

Okay i'll try this

[bap-dev]

Still asking myself about the reason why an older version is availible but not a newer one... and how long will the old one stay alive...

[neoighodaro]

probably not long but at least i can buy some time to test an upgrade to 15...

[bap-dev]

probably not long but at least i can buy some time to test an upgrade to 15...

good point!

[andrewlecuyer]

This thread appears to already cover many of the pertinent details, but I will clarify the following:

• Any Postgres 14 images that you have used in the past (e.g. the crunchy-postgres:ubi8-14.10-0 image, as referenced in this thread) are still available.
• You can then leverage the Postgres major version upgrade feature available in Crunchy Postgres for Kubernetes to get onto a major version of Postgres available via the Crunchy Developer Program.

Additionally, I'll note that the Supported Platforms page is a great resource to get insight into Postgres version availability.

I also recommend subscribing to the Developer program mailing list via the following page for the latest updates about Postgres version availability:

https://www.crunchydata.com/developers/download-postgres/containers

Hope this helps!

[budimanjojo]

@andrewlecuyer Thanks for the response!

I think the question from me is why is this line here:

postgres-operator-examples/helm/install/values.yaml

Line 20 in 9cbce08

image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.11-0

Got updated from this PR: #254

Can the default value be reverted back to registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.10-0 so it doesn't defaulted to a non-existance image?

[andrewlecuyer]

@budimanjojo sorry about the confusion!

The image tag you referenced actually shouldn't have been included, and has since been reverted/removed.

This means Crunchy Postgres for Kubernetes will no longer attempt to rollout a non-existent image tag after upgrading, and any existing clusters will simply remain running with their current image tags (giving you a chance to upgrade Postgres, etc. as described above). Or you can always customize the install with additional related images as well.