zalando
Missing images for release v1.15.0
Hello,
Release v1.15.0 includes three Docker images (Postgres Operator, UI, Logical Backup). However, only the Postgres Operator image has been published yet. The following images are currently missing:
- ghcr.io/zalando/postgres-operator/logical-backup:v1.15.0
- ghcr.io/zalando/postgres-operator-ui:v1.15.0
Is it planned to publish the missing images?
Hi,
yes, the UI and logical backup images are indeed missing because the github pipeline to build them fails at the UI step. Not great that this pipeline is only triggered on release. It seems that the new python slim base image does not contain python3-distutils anymore. We need to update the UI Dockerfile accordingly so that it works with all our pipelines again. For 1.15.0 it's too late now I guess. I hope, I can follow up with 1.15.1 next week.
Yeah I haven't merged it to the gh-pages branch yet, from where we publish the charts. They are relying on the ghcr images and for the UI release it would fail to start then. So I choose to wait until the problem is fixed.
The helm chart is missing too?
At least I found the "chart" archive on the master branch via /charts/postgres-operator/postgres-operator-1.15.0.tgz. At least I can perform a partial upgrade already.
@FxKu, the release of 1.15.1 is over a month "overdue" on GitHub. Is there an ETA for this fix?
Alternatively, is it safe to downgrade the operator so get logical backups working again?
CloudNativePG seems to be the current standard, we are planning to move to it. Broken releases for databases are a big no-no, if they stay broken for 2 months I am never coming back.
@remram44 I'm sorry, I think I'm tired. Have you read the license?
THE SOFTWARE IS PROVIDED "AS IS",
I'm a user here, but part of the free software community. Nobody is forcing you to use this or that. Do whatever :)
Taking the opportunity to thank every contributor here! Thanks for your hard work!
(And hide my comment as it is clearly out of topic like the previous one :) )
Nobody is forcing you to use this or that
and as I said I'm not. It's not because the maintainers have moved on to other things that the users suddenly stop needing a database operator, so I am pointing out a replacement for them.
Ok, sorry for the long wait. We've finally fixed the build process for the UI image and were able to release latest helm packages. Closing this issue.