Problem

As of August 28th, 2025, Bitnami will implement some changes:

• Disable image generation and move existing ones to a "Bitnami Legacy" repository: All existing container images and versioned tags will move from docker.io/bitnami to docker.io/bitnamilegacy
• The legacy repository will receive no updates, fixes, or support
• Only a focused set of hardened images will remain in the main repository, available only with "latest" tags

We currently use Bitnami charts and images for several external components in our demos and documentation, including PostgreSQL, Redis, OpenLDAP, and MinIO.

A solution needs to be merged before August 28, 2025 to ensure demos and getting started guides continue to work.
TBD if we want to implement the quick solution first or directly start implementing the long-term solution.

The first step is to find all instances where we use Bitnami charts and images.

Quick Solution

• Migrate to Legacy Repository: Update all affected charts and images to point to the bitnamilegacy repository as a temporary workaround
• Set Helm chart value global.security.allowInsecureImages=true where necessary
• Test all affected demos and documentation

PRs

• chore: update tests and docs to use bitnamilegacy druid-operator#744
• chore: fix minio Chart values for bitnami migration druid-operator#745
• chore: update docs and examples to use bitnamilegacy druid-operator#747
• chore: update Helm chart and docs to use bitnamilegacy trino-lb#88
• chore: update tests and docs to use bitnamilegacy hive-operator#622
• chore: fix minio Chart values for bitnami migration hive-operator#623
• chore: update docs and examples to use bitnamilegacy hive-operator#625
• chore: update tests and docs to use bitnamilegacy superset-operator#655
• chore: update docs and examples to use bitnamilegacy superset-operator#657
• chore: update tests and examples to use bitnamilegacy trino-operator#784
• chore: update examples to use bitnamilegacy trino-operator#787
• chore: update docs to use bitnamilegacy stackablectl#405
• chore: update demos to use bitnamilegacy demos#290
• chore: update demos to use bitnamilegacy demos#297
• chore: update tests to use bitnamilegacy spark-k8s-operator#598
• chore: update example to use bitnamilegacy spark-k8s-operator#601
• chore: update tests and docs to use bitnamilegacy airflow-operator#670
• chore: update docs and examples to use bitnamilegacy airflow-operator#672
• chore: update tests to use bitnamilegacy nifi-operator#846
• chore: update examples to use bitnamilegacy beku.py#37

Long-term solution

Research and evaluate alternative providers for each component.

Since these components currently seem to serve demonstration purposes only and are not meant to be used in production the way we deploy them, we could create our own small Helm charts, either from scratch or fork existing ones.
I found this repo which could be an interesting base to fork from, it contains Postgres, Redis and Valkey.

The Bitnami project continues to make its source available at bitnami/containers under the Apache 2 license; images can be built from source.

We could also build the image from source and put them in our OCI registry

We could also integrate solutions from other providers:

Ideas for Postgres:

• https://github.com/CrunchyData/postgres-operator
• https://github.com/zalando/postgres-operator

Ideas for OpenLDAP:

• https://github.com/jp-gouin/helm-openldap

Ideas for MinIO:

• We have a Nuclino page with MinIO alternatives
• Otherwise: https://github.com/minio/operator/tree/v5.0.18/helm/operator

Ideas for Redis:

• Switch to valkey (I didn't find a widely supported Helm chart except for the Bitnami one)
• Switch to DragonflyDB: https://www.dragonflydb.io/docs/getting-started/kubernetes