Migrating Bitnami to Bitnami Legacy
Introduction
Bitnami is moving most container images to a legacy repository on August 28th, 2025, and stopping updates. If you're using Bitnami images or Bitnami Helm charts, your deployments will break when they try to pull images that no longer exist.
Critical Impact: This affects all Bitnami users regardless of environment. Expect immediate pod failures, CI/CD pipeline breaks, and potential downtime requiring immediate remediation.
But What is Bitnami?
For 18 years, Bitnami made life easier for developers. They packaged popular software like databases, web servers, and apps into ready to use containers and Helm charts.
The best part? It was all free. Until Broadcom bought VMware, now Broadcom wants to charge $50,000-$72,000 per year for what used to be free.
Goal
Why did we make this rule book?
To avoid insecure, inconsistent, or incomplete Bitnami-based deployments.
To prevent operational disruptions caused by image migration to the legacy repository.
What will you achieve?
Reliable deployments by migrating to the correct image repository
Clear, repeatable migration workflows for Helm charts and container images
Reduced operational risk during and after Bitnami’s transition
Who is this for?
Developers, DevOps, and platform engineers responsible for maintaining workloads built on Bitnami Helm charts or container images.
Workflow
This workflow ensures a consistent migration of Bitnami images and Helm charts to the Bitnami Legacy repository without downtime. Stakpak uses this rule book to check, update, and validate deployments, making the process secure and reproducible across environments.
Preparation
Audit workloads pulling images from
docker.io/bitnami.Review Kubernetes manifests and Helm charts for Bitnami image references.
Document affected services and environments.
Update References
Change image references from:
docker.io/bitnami/<image>→docker.io/bitnamilegacy/<image>
Update Helm chart repository sources to use the Bitnami Legacy repo.
Validation
Deploy changes in a staging environment.
Run integration tests to confirm application stability.
Verify results of security scans.
Rollout
Apply updates incrementally using rolling deployments.
Monitor logs, health checks, and performance metrics during rollout.
Keep rollback procedures ready for unexpected issues.
Use Cases
References
Last updated