# Advisory: Bitnami Catalog Changes and Impact on MOSIP Deployments **URL:** \ **Category:** General\ **Tags:** announcement, identity\_platform\ **Created:** [September 19, 2025, 11:11am UTC](https://community.mosip.io/t/advisory-bitnami-catalog-changes-and-impact-on-mosip-deployments/2311 "2025-09-19T11:11:22Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Varaniya1](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/varaniya1/32/1322_2.png) [@Varaniya1](https://community.mosip.io/u/Varaniya1)\ **Post date:** [September 19, 2025, 11:11am UTC](https://community.mosip.io/t/advisory-bitnami-catalog-changes-and-impact-on-mosip-deployments/2311/1 "2025-09-19T11:11:22Z")
## 📢 Bitanmi Major Changes and Impact on MOSIP Identity Platform Bitnami (now under Broadcom) has announced **major changes to its open-use catalog of container images and Helm charts**. Many artifacts that were previously available as open source will either: - Move to **legacy repositories** (with no further updates/security patches), or - Require a **paid subscription** for continued access and updates. This advisory highlights: - What is changing - How it may affect MOSIP and partners - Immediate steps you should take - Alternative solutions to evaluate ## What is Changing Based on public announcements, GitHub issues, and community reports: - **Deprecation of versioned images** : - From **August 28, 2025** , most versioned tags in [`docker.io/bitnami`](http://docker.io/bitnami "http://docker.io/bitnami") has been moved to [`docker.io/bitnamilegacy`](http://docker.io/bitnamilegacy "http://docker.io/bitnamilegacy"). These will receive **no updates or security patches**. - **Only “latest” free images remain** : - A small “hardened” subset will remain available under the `latest` tag, primarily for **development/non-production use**. - **Paid offering – Bitnami Secure Images** : - Full catalog with versioned tags, updates, and enterprise support will be accessible only via paid **subscription**. - **Helm charts** : - **Brownouts & final cutoff** : - Temporary outages: **Aug 28–29, Sept 2–3, Sept 17–18, 2025** - **Final removal / cutoff: Sept 29, 2025** ## Impact on MOSIP & Partners If your deployment uses Bitnami charts/images for **Keycloak, MinIO, Kafka, PostgreSQL, Redis, ActiveMQ** , etc. You may encounter: - **Image pull failures** (`ErrImagePull`, `ImagePullBackOff`) - **Broken CI/CD pipelines** when versioned tags disappear - **Security risks** from unpatched legacy images - **Operational instability** during scaling, upgrades, or restarts ## Recommended Actions ### Immediate (within Next Few Weeks) 1. **Inventory usage** – Identify all Bitnami images/charts in your environment. 2. **Override repos/tags** – Update Helm values/manifests to reference `bitnamilegacy` or your own registry. 3. **Mirror critical images** – Pull/store images locally to avoid availability issues. 4. **Update CI/CD pipelines** – Make image references configurable. 5. **Test during brownouts** – Validate that systems remain functional when Bitnami images are unavailable. ### Medium Term - **Evaluate alternatives** – Official charts/images (Keycloak, MinIO, Kafka via Strimzi, etc.) - **Self-host or mirror** – Maintain critical images in your own registry. - **Standardize migration strategy** – Define versioning, patching, and security update policies. - **Update documentation** – Ensure partners and implementers are aligned. ## Suggested Alternatives | Component | Alternatives | Notes | | --- | --- | --- | | **Keycloak** | Official Helm chart, community operators | Avoid Bitnami lock-in | | | | | | **MinIO** | Official MinIO charts/images | Full control, HA may need setup | | | | | | **Kafka** | Strimzi Operator, Apache Kafka operator | Strong community support | | | | | | **Postgres / Redis / ActiveMQ** | Community/vendor images; managed DB services | Check cost, lock-in, backup needs | | | | | ## Suggested Timeline for Partners - **Immediately (within next week)** → Inventory usage, start overriding repos/tags, test migration paths. - **Aug 28 – Sept 29, 2025** → Migrate high-risk components, ensure no dependency on deprecated repos. - **After Sept 29, 2025** → All production workloads should use **maintained, supported images**. ## Conclusion MOSIP **strongly advises** partners, countries, and community users to **migrate away from Bitnami’s free catalog** for any production-critical services. Continuing to rely on deprecated images will expose systems to **security vulnerabilities, failures, and instability**. **Discussion & Support:** Please use this **community forum** to share your migration plans, ask questions, and raise any blockers. The MOSIP team and other community members will provide guidance and support collaboratively. ## References To know more about the changes regarding bitnami you can refer below links: 1. [Upcoming changes to the Bitnami catalog (effective August 28th, 2025) · Issue #35164 · bitnami/charts · GitHub](https://github.com/bitnami/charts/issues/35164?utm_source=chatgpt.com) ]( [Upcoming changes to the Bitnami catalog (effective August 28th, 2025) · Issue #35164 · bitnami/charts · GitHub](https://github.com/bitnami/charts/issues/35164?utm_source=chatgpt.com) ) 2. [Bitnami Secure Images Overview](https://techdocs.broadcom.com/us/en/vmware-tanzu/bitnami-secure-images/bitnami-secure-images/services/bsi-doc/overview.html?utm_source=chatgpt.com) 3. [Broadcom Introduces Bitnami Secure Images For Production-Ready Containerized Applications - Broadcom News and Stories](https://news.broadcom.com/app-dev/broadcom-introduces-bitnami-secure-images-for-production-ready-containerized-applications?utm_source=chatgpt.com) ---
**Author:** ![Varaniya1](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/varaniya1/32/1322_2.png) [@Varaniya1](https://community.mosip.io/u/Varaniya1)\ **Post date:** [September 19, 2025, 11:12am UTC](https://community.mosip.io/t/advisory-bitnami-catalog-changes-and-impact-on-mosip-deployments/2311/2 "2025-09-19T11:12:05Z")
---
**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/f60a343830fe848c9a68e2d1cc654d0cb7fbbaf2.svg) [@system](https://community.mosip.io/u/system)\ **Post date:** [September 29, 2025, 11:12am UTC](https://community.mosip.io/t/advisory-bitnami-catalog-changes-and-impact-on-mosip-deployments/2311/3 "2025-09-29T11:12:49Z")
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed. ---
**Author:** ![reshamchugani](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/reshamchugani/32/863_2.png) [@reshamchugani](https://community.mosip.io/u/reshamchugani)\ **Post date:** [October 30, 2025, 4:17am UTC](https://community.mosip.io/t/advisory-bitnami-catalog-changes-and-impact-on-mosip-deployments/2311/4 "2025-10-30T04:17:59Z")