I recently started at a company and found out they've been delaying decisions on how to handle Bitnami's transition to paid images. The person who brought me on has left, and now I'm tasked with figuring out the best approach. I'm curious about how others have dealt with this situation. What strategies did your teams adopt?
5 Answers
We've chosen to switch to alternative images wherever possible and asked the team to look for replacements for those we couldn't switch immediately. It’s definitely a priority.
Bitnami provides all the build receipts, which means you can rebuild and manage them as per your needs using the upstream repos. Just bear in mind that Bitnami often customizes their images, so if you fork their charts and maintain them yourself, you're committing to do so forever.
It wasn't really the organization's fault for delay; Bitnami's announcement came unexpectedly. I'd suggest taking the images you need and uploading them to your own registry. That gives you some breathing room to look for alternatives or even create new images.
For Postgres, we found CloudNativePG to be a fantastic alternative. It offers features like reader replicas and auto failovers, which we love. Our team even considered migrating away from AWS RDS to save costs, and it runs smoothly!
One approach we took was switching to Bitnami Legacy to avoid any downtime while we gradually transitioned our systems. There’s definitely some time to migrate properly.

Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically