←back to thread

The Deletion of Docker.io/Bitnami

(community.broadcom.com)
329 points zdkaster | 1 comments | 28 Aug 25 04:37 UTC | HN request time: 0.205s | source
Show context
imiric ◴[28 Aug 25 07:17 UTC] No.45049377[source]▶
I was never a fan of images from Bitnami. They always used complicated entrypoint and setup scripts, and introduced weird quirks to the software. More than once have I experienced issues or ran into configuration limitations with Bitnami images that didn't exist in official ones.

So good riddance, as far as I'm concerned. I recommend anyone to avoid using them, and switch to official images or to build them yourself if they're not provided. That's the more secure approach, anyway.

replies(3): >>45049579 #>>45049627 #>>45050894 #
1. Xeago ◴[28 Aug 25 07:50 UTC] No.45049579[source]▶
I concur. There was supposedly a migration path from their postgresql image & chart to the postgresql-ha image & chart.

Aside of having to re-mount the data disk and move things around manually; the -ha chart has numerous other issues where it always requires the master to be node-0. And with pods being rescheduled within a statefulset, good look having the master be on node-0. If there was an outage and the master is anywhere else, node-0 will just 'wait' for a master to come online, time out and shoot itself in the head thinking it is in a network partition and that retrying may help.

The algorithm implemented by postgresql-ha turned out to be plain broken. Only able to survive pods neatly shutting down.