[Housekeeping] Bitnami public repository deprecation

[aurbano]

Describe the issue

Bitnami has announced the deprecation of their public repository: https://github.com/bitnami/charts/issues/35164

All existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be moved from the public catalog (docker.io/bitnami) to the Bitnami Legacy repository (docker.io/bitnamilegacy). This legacy catalog will receive no further updates or support and should only be used for temporary migration purposes.

Suppose your deployed Helm chart is failing to pull images from docker.io/bitnami. In that case, you can resolve this by subscribing to Bitnami Secure Images, ensuring that the Helm charts receive continued support and security updates. As a temporary workaround, you can upgrade to the same version and update the repository parameter for each container image to the Bitnami Legacy repository.

If I understand the announcement correctly all images will be moved to the legacy repository, and only the latest image will be available to free-tier users.

What if we do not do this?

Flyte may not be able to make all new Helm charts versions available unless users are on a paid Bitnami plan

Related component(s)

No response

Are you sure this issue hasn't been raised already?

• [x] Yes

Have you read the Code of Conduct?

• [x] Yes

[welcome[bot]]

Thank you for opening your first issue here! 🛠

[runllm[bot]]

Your understanding is correct: Bitnami is deprecating their public repository, moving older images to a legacy repository, and restricting free-tier users to only the latest versions of a limited set of images. This means Flyte deployments that rely on specific Bitnami image versions (e.g., for dependencies like Postgres, Redis, Minio, Contour) may face issues unless users subscribe to Bitnami Secure Images or update their deployments to use only the latest available images. This could impact Flyte's ability to provide fully functional Helm charts for all users in the future, especially for those needing older or specific image versions.

If Flyte does not address this, users may encounter failed deployments or unsupported configurations unless they migrate to the new Bitnami model or use alternative images. For more details, see the Bitnami deprecation announcement. Would you like more detail on mitigation strategies or alternative approaches?

Sources:

• Bitnami deprecation announcement

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @runllm to ask follow-up questions. See runllm.com for more!

[Sovietaced]

Flyte seems to be using pinned docker images so I don't think it will be hard to change the repository to bitnami legacy. It might be a little more challenging to deal with pinned helm charts, which have default images in their generated manifests.