fix(deps): Use bitnami images from docker.io/bitnamilegacy

[RisingOpsNinja]

Bitnami has recently announced breaking changes to there public catalog bitnami/charts#35164 already discussed in issue #600

Since August 28th the charts and the docker images have not received updates and on September 29th the docker images will be moved to docker.io/bitnamilegacy which breaks the chart.

Switch to docker.io/bitnamilegacy to be able to pull images beyond that date as a temporary workaround.

[Mart-Kuc]

I’d like to open a discussion about which registry we should adopt going forward.
Currently, we have two options:

1. Legacy Bitnami Docker registry

• Contains older images, but they no longer receive updates.

• Likely to be removed in the near future (this is only my assumption, not based on official information).

2. Bitnami secure images

• Only the latest tag is available.

• We have no control over which version “latest” points to, which may introduce instability in production.

Additionally, we’ll need to update the Helm registry to the OCI format:
oci://registry-1.docker.io/bitnamicharts/

What are the community’s suggestions or opinions on this?

[nijel]

Isn't there some alternative to Bitnami? Migration between PostgreSQL versions is AFAIK not automatic, so having a movable latest tag for it seems annoying for production. For Redis it would not be that much of an issue; I haven't seen compatibility issues there. Still, you mostly want a fixed tag in production environment...

[RisingOpsNinja]

The helm charts of groundhog2k are a promising alternative. They use unmodified docker library images:

• postgresql: https://artifacthub.io/packages/helm/groundhog2k/postgres
• redis: https://artifacthub.io/packages/helm/groundhog2k/redis

Source: https://github.com/groundhog2k/helm-charts/tree/master/charts

I already migrated a deployment successfully, but manual steps are required.

[Mart-Kuc]

I double-checked the versions currently used in the Helm chart:

• Postgres: chart version 16.7.15 → image version 17.5.0-debian-12-r16 (this image is available in the legacy Bitnami Docker registry).
• Redis: image tag version 8.0.2-debian-12-r3.

My suggestion is to explicitly pin these image tags in our values.yaml:

• Postgres → 17.5.0-debian-12-r16

• Redis → 8.0.2-debian-12-r3

This ensures consistency between environments and avoids unexpected changes in production. It will not break anything on the community side. If, in the future, Bitnami removes the legacy registry, we can switch to another source (for example: Groundhog2k Postgres

Of course, please feel free to correct me if I’ve got the versions wrong or if this approach doesn’t make sense.

[Gilderko]

Hello, I would suggest temporarily moving to bitnami/legacy, since relying only on the latest tag (as required by Bitnami’s recent changes) is not suitable for production environments. Later on, a more suitable and reliable source of PostgreSQL Helm charts can be found—or even consider maintaining one explicitly for Weblate.

At the moment, any k8s deployments can not really work until the Helm chart is updated, so it would be beneficial if this could be resolved please.

[tarioch]

I would also suggest moving temporarily to bitnamiclegacy (to make it installable again) and then as a second step to migrate to something else such as groundhog2k. I've also moved some personal charts of to groundhog2k and works well.

[masterkain]

yeah we gotta move away from bitnami. this is just part of the current nightmare we're facing atm with bitnami pulling stunts

[nijel]

Okay, I've just merged this.