Bitnami images no longer updated

[jceb]

Describe the bug a clear and concise description of what the bug is.

Bitnami's recent change (bitnami/charts#35164) breaks redis and mongodb in this chart. Alternatives should be considered.

What's your helm version?

3.17.3

What's your kubectl version?

1.33.1

What's the chart version?

7.14.6

Enter the changed values of values.yaml?

We added the following settings to values.yaml to switch to the legacy images provided by bitnami:

mongodb:
  image:
    repository: bitnamilegacy/mongodb

redis:
  image:
    repository: bitnamilegacy/redis

[filippo-clearml]

Overview

In short, to resolve this promptly, new ClearML Helm Chart releases are now available. Please deploy this update before August 28th to avoid any issues.

If you’re running your own MongoDB or Redis deployments and have disabled the built-in dependency charts used by the ClearML Helm Chart, you are not affected on the ClearML side.

Breakdown

On August 28th, the images referenced in Bitnami dependency charts will be moved to a new container registry.

Although older images may still be cached locally, we recommend updating before August 28th to prevent potential deployment issues if the cache is cleared, nodes are disrupted, or deployments restart and attempt to pull from outdated registry locations.

What You Need to Do

Please review and apply the changes relevant to your environment before August 28th to maintain seamless deployment operations.

For Non-Air-Gapped Systems

Depending on your environment, proceed with one of these options:

• If you plan to upgrade your release - Upgrade to the latest ClearML Helm charts. Before upgrading, verify that your custom override values do not contain any image overrides that would prevent Helm from applying the updated image references.

• If you want to stay on your current release. Edit your custom override values file to point to the new registry. We’ve included a full reference to the impacted YAML files per Helm chart below.

For Air-Gapped Systems

No action is required as long as all required images are already downloaded and available inside your cluster.
For future upgrades, continue your usual image download process. Upstream charts will already reflect the new registry paths.

---

YAML References

In the clearml chart:

redis:
  image:
    repository: bitnamilegacy/redis
mongodb:
  image:
    repository: bitnamilegacy/mongodb

In the clearml-serving chart:

kafka:
  image:
    repository: bitnamilegacy/kafka
  zookeeper:
    image:
      repository:  bitnamilegacy/zookeeper

[igor-soldev]

Hi @filippo-clearml,

Thanks for the update.

One important note regarding the bitnamilegacy images: as the name implies, these are effectively frozen and will not receive future security updates. While they solve the immediate deployment issue, relying on them poses a long-term risk.

Proposed Solution for Kafka

For the Kafka component in clearml-serving, I suggest switching to soldevelo/kafka.
It is an actively maintained, drop-in replacement that preserves the Bitnami directory structure and environment variables. This ensures the chart continues to work without refactoring, but with the benefit of receiving updates.

Suggested update for clearml-serving:

kafka:
  image:
    repository: soldevelo/kafka # Replaces bitnamilegacy/kafka

I can submit a PR to update the Kafka image reference if you are interested in moving off the frozen legacy track for this component.