How Bitnami Registry Changes Impact Exivity Kubernetes Deployments
Bitnami has recently announced significant changes to its distribution of container images. If your Exivity deployment on Kubernetes uses the built-in PostgreSQL or RabbitMQ Helm charts, these changes directly affect you.
As of August 28, 2025, Bitnami began deprecating most of its free, versioned container images from the main Docker Hub repository (docker.io/bitnami). This shift is already causing issues such as image pull failures and pod restarts, especially in environments that depend on the now-deprecated image paths.
🗓️ Bitnami Deprecation Timeline
- August 28, 2025: Deprecation begins, images start migrating to a legacy registry
- August 28–29, September 2–3, September 17–18: Scheduled brownouts impact availability
- September 29, 2025: Complete removal of Bitnami public images from
docker.io/bitnami
🛠️ How This Affects Exivity Users
If you're using Exivity's default embedded PostgreSQL and RabbitMQ charts, you may encounter:
- Deployment errors due to missing images
- Failure to scale or restart pods
- Unexpected downtime in non-production environments
🔧 Immediate Workarounds
We’ve published a detailed guide to help you work around the issue while preparing for a long-term solution.
👉 Read the full hotfix instructions here:
In short, there are two options:
- Upgrade to Exivity v3.36.1 or later (Recommended)
- Apply a temporary patch to point to Bitnami’s legacy registry
⚠️ The legacy registry is intended as a temporary fix only
🚨 Production Considerations
Best Practice: Do not use the embedded PostgreSQL and RabbitMQ charts in production.
For production-grade reliability and security, we recommend transitioning to managed services or dedicated self-hosted solutions.
Managed Services (Preferred)
- PostgreSQL: AWS RDS, Azure Database for PostgreSQL, Google Cloud SQL
- RabbitMQ: Amazon MQ (RabbitMQ), CloudAMQP, Aiven for RabbitMQ
Self-Hosted Alternatives
Use official Docker images or dedicated Helm charts like:
- CloudNativePG for PostgreSQL
- RabbitMQ Cluster Operator
🔄 Migration Path Coming Soon
We're actively preparing comprehensive documentation to support users moving to fully self-hosted or managed database solutions. This will include:
- Detailed Helm configurations
- Migration instructions
- Long-term support guidance
Stay tuned for an upcoming announcement.
🔍 Behind the Bitnami Change
Bitnami is restructuring its container image strategy:
- Free images will now only support the latest tags and are not recommended for production use.
- Versioned images have been moved to
docker.io/bitnamilegacy, a temporary and unsupported registry. - Bitnami Secure Images (BSI) is a new commercial option that offers enterprise-grade support and security.
Resources:
✅ What You Should Do Next
- If you’re running Exivity in production, migrate to a managed or self-hosted solution
- If you're in a dev/test environment, apply the hotfix, but plan your migration
- Upgrade to Exivity v3.36.1+ to ensure compatibility with the latest container registry configurations
