bitnami legacy charts

[guimoreirar]

Name and Version

bitnamilegacycharts/*

What is the problem this feature will solve?

I downloaded different Helm charts from the new legacy repository:

helm pull oci://registry-1.docker.io/bitnamichartslegacy/<chart-name> --version <version> --untar

In the default values.yaml, image is still pointing to repository docker.io/bitnami:

image:
  registry: docker.io
  repository: bitnami/<chart-name>

According to the announcement, after August 28, 2025, versioned images will no longer be available under docker.io/bitnami/. They will either be moved to bitnamilegacy/ (without updates) or require a subscription to Bitnami Secure Images.

This means that the current legacy charts will eventually break if users deploy them without overriding the image repository.

What is the feature you are proposing to solve the problem?

To help users transition smoothly after the upcoming Bitnami catalog changes, it might be helpful if the charts under the bitnamichartslegacy repo pointed by default to docker.io/bitnamilegacy/....

This way, deployments would continue to work out of the box even after the changes take effect.

[carrodher]

Thanks for raising this! Let me clarify a few points:

1. Helm charts under bitnamicharts are not going to be removed. The bitnamichartslegacy namespace was created mainly for consistency with the container image migration, but it’s not actually needed for Helm charts and may be removed.
2. Helm charts under bitnamicharts will not be updated anymore. You can still deploy them, but you’ll need to override the image registry from docker.io/bitnami to docker.io/bitnamilegacy. This can be done either with --set at install/upgrade time, or by editing your values.yaml.

The source code of the Helm charts will continue to be open source in this repo, referencing docker.io/bitnami in their default values.yaml, but this does not mean they’ll stop working. As long as you override the registry/repository to bitnamilegacy, you’ll be able to keep deploying them.

[jamsyoung]

So people don't feel crazy. For an unspecified amount of time, enough for our alerts to go off, around 1:00pm EST, these images were not available. They are now, as of the writing of this comment, but yesterday we were getting

➜ docker pull docker.io/bitnami/external-dns:0.18.0
Error response from daemon: failed to resolve reference "docker.io/bitnami/external-dns:0.18.0": docker.io/bitnami/external-dns:0.18.0: not found

[carrodher]

So people don't feel crazy. For an unspecified amount of time, enough for our alerts to go off, around 1:00pm EST, these images were not available. They are now, as of the writing of this comment, but yesterday we were getting

$ docker pull docker.io/bitnami/external-dns:0.18.0
Error response from daemon: failed to resolve reference "docker.io/bitnami/external-dns:0.18.0": docker.io/bitnami/external-dns:0.18.0: not found

As announced in #35164, as part of the postponement, a series of brownouts will occur.

The affected applications for each brownout are listed in the same issue (see #35164 (comment)). In this case, external-dns was part of the first brownout, which explains the issue you observed. That brownout started on August 28 at 08:00 UTC and lasted 24 hours.

[carrodher]

1. Helm charts under bitnamicharts are not going to be removed. The bitnamichartslegacy namespace was created mainly for consistency with the container image migration, but it’s not actually needed for Helm charts and may be removed.

Quote replying to myself: The unused bitnamichartslegacy registry has been removed and is now empty. This registry wasn’t necessary since bitnamicharts will not be cleaned up, so unlike the container case, no backup was required.

[BowlingX]

I think this should have been written a bit more clearly within #35164. It was unlclear for some time what happens exactly to the helmcharts, so logically - it would have made sense to use bitnamichartslegacy...and now its gone :(.

[carrodher]

I think this should have been written a bit more clearly within #35164. It was unlclear for some time what happens exactly to the helmcharts, so logically - it would have made sense to use bitnamichartslegacy...and now its gone :(.

The bitnamichartslegacy registry was never part of any official announcement or blog post. It was only explained directly to users who happened to come across it, but it was not an officially supported or announced backup registry for charts.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.