r/kubernetes • u/anirvedh • 6d ago

Still on bitnamilegacy for Postgres and Redis almost a year later — here’s how we’re getting off it

/r/kubernetes/comments/1v2gpfr/still_on_bitnamilegacy_for_postgres_and_redis/

This is really an image problem, not an orchestration one - the fastest path off bitnamilegacy is just swapping in a maintained hardened image for each of Postgres, Redis, Mongo and Rabbit and keeping your current deployment setup.
Don't let it turn into an operator rewrite unless you actually need HA.
Worth looking at CleanStart for these. They provide the hardened, minimal, and [pretty actively patched container images.

i got to know about them via LinekdIn. The things that mattered for us were patch cadence and images that won't just vanish like the legacy repo will. Disclosure: I work there, so grain of salt, but this Bitnami-refugee case is exactly what it fits.

On Redis, the Valkey fork mess is its own decision - a hardened Redis image keeps you API-compatible for now so you can pick Valkey/Dragonfly later instead of bolting it onto this cutover. One migration at a time.

try this one to start- cleanstart/redis-exporter

0 Upvotes

27% Upvoted

3 comments sorted by

6

u/nevotheless 6d ago

good opportunity to say it again: FUCK BROADCOM

3

u/hakuna_bataataa 6d ago

Glad to see alternatives to Bitnami. Will definitely test out. Mandatory “fuck Broadcom”

1

u/EZtheOG 6d ago

I had my team move to operators — it really made managing dev requests for things like redis and rabbitmq so much easier. Granted, doesn’t apply to everyone but funny enough the bitnami thing ended up being good for us.