postgres-operator: This container version is no longer available from the Crunchy Data Developer Program.

Sorry but I am still confused. We are using PGO v5 with the recommended images from the installation instructions, but pulling those still fails. If that is desired behavior, this should be made clear in the documentation and those images should be removed from the official examples.

See also: https://github.com/CrunchyData/postgres-operator-examples/issues/190

Are there any images that can be used for PG13 at this moment?

I think, from a user’s perspective, the best way to avoid such scenarios in the future is to use a local proxy cache for the images.

I have the same problem. I try to update the version of image with the last example and it’s the same. Perhaps it’s a registry problem.

All my production cluster is currently broken 😦

Sorry to hear about this issue. There has been some discussion of this in past GitHub issues and communications through various channels, but the short answer is that Crunchy Data makes available the last two Postgres versions as part of the Postgres Developer program. We’ve sent out notifications on our developer mailing list regarding this and would recommend subscribing there.

Developer portal images are not intended for production use. But we very much do not want folks to be in a bad place. If you have feedback on how we could better improve communication would welcome that feedback. At the moment we’re exploring how to better enhance and improve the community around this so hopefully that helps in the future.

If you can contact us at info@crunchydata.com we are happy to help you upgrade or if you need support for running in production would be happy to have a conversation around Crunchy Postgres for Kubernetes.

@luatnd we are not seeing any issues pulling the image:

 % podman pull registry.developers.crunchydata.com/crunchydata/postgres-operator:ubi8-5.4.2-0
Trying to pull registry.developers.crunchydata.com/crunchydata/postgres-operator:ubi8-5.4.2-0...
Getting image source signatures
Copying blob sha256:ba5bedb8c7e8b3d862ba4d517d65bd544c01cf5549d58d9e4efb87bed7cfef74
Copying blob sha256:96aaf4ff1a6663ef5e5081b8f83265acd80a5a4e725bfac21bf247b1ce6bb252
Copying blob sha256:8b44edf5cc0f19a3d65b8145b40e7f3205de7a90efb7a13572ec376e93b0ac96
Copying config sha256:f40fc1e57fcb014451e7c12a5abbd5181aa4981b82a75937b4b4faeb87209835
Writing manifest to image destination
f40fc1e57fcb014451e7c12a5abbd5181aa4981b82a75937b4b4faeb87209835

Therefore, the issue does not appear to be with the registry.

Is the issue still occurring? If so, perhaps there is a network issue on your end?

Thank you for clarifying. v5 has been a todo for a long time for us, but for other reasons that I can’t address today, I’m stuck on an EOLed k8s version that’s not compatible with pgo v5 (at least the latest).

Honestly the best option for me now seems to be to take the images I depend on and push them to a registry I control, from the one of the nodes that has already pulled them. This feels vaguely dirty.

I mean, 4.7.10 was released yesterday, I just tried to upgrade via helm and that fails because the images aren’t available. This doesn’t seem to be tied to pg version either, this image failed to pull: registry.developers.crunchydata.com/crunchydata/pgo-deployer:ubi8-4.7.10.

I’m watching operator releases and a few issues in this repo, and I had no clue this was coming.

The ideal place to follow for updates on releases, end of builds, etc. is on our mailing list. Would recommend joining it at https://www.crunchydata.com/developers/download-postgres/containers.

4.7.10 is intended more as a LTS for paying customers, but has been in feature freeze for some time.

As mentioned elsewhere, v5 and the subsequent versions over the last two years have a number of improvements and make keeping current with modern K8s versions much easier thus we recommend getting to those more modern versions.

@craigkerstiens Would be great to understand what “developer portal images” means. Installing v5 of the operator via the registry (predictably) installs images from that registry. I’m probably reading this wrong, but I’m reading it as “when you install pgo, you are going to be using images not intended for production.”

It kinda seems like you just deleted all the 4.x images from your image repo, and you kinda acknowledge that the communication wasn’t great. Hard to feel really good about this from my perspective.

The same applies to me. I have problem with pulling image: registry.developers.crunchydata.com/crunchydata/crunchy-postgres:ubi8-13.8-1