Upcoming changes to the Bitnami catalog

[spyesx]

According to Upcoming changes to the Bitnami catalog (effective August 28th, 2025) #35164 on bitnami/charts, the bitnami/helm repository will not be freely available from 2025-08-28.

Is there any plans to overcome it within directus helm chart? Are you planing to import it in house?

# https://github.com/directus-labs/helm-chart/blob/master/charts/directus/Chart.yaml#L25
dependencies:
- name: mysql
  version: "~13.0.0"
  repository: "https://charts.bitnami.com/bitnami"
  condition: mysql.enableInstallation
- name: postgresql
  version: "~16.7.8"
  repository: "https://charts.bitnami.com/bitnami"
  condition: postgresql.enableInstallation
- name: redis
  version: "~21.1.11"
  repository: "https://charts.bitnami.com/bitnami"
  condition: redis.enabled

[mykhailo-sindieiev]

Hello, thank you for raising this. Yes, I see several options here. Probably, we might face problems with mysql chart because I do not see it in the bitnamisecure repo. I do see postgres and redis images in that registry, so I believe bitnami will keep maintain them with the latest tag which I believe will not affect Directus installation. So, to resolve the potential issue with mysql I think I will prepare a new release with official MySQL helm chart - https://github.com/mysql/mysql-operator/tree/trunk/helm/mysql-innodbcluster

Another option would be to temporarily pin Directus helm chart to the bitnami's legacy repo

[spyesx]

Sure, you're welcome.

Bitnami announced it is migrating all charts and images. If they are "still here" it is only temporary. That includes MySQL and PostgreSQL.

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.

While Directus is compatible with multiple DB, they recommend PostgreSQL. The current chart could support these DBs on its own without relying on thirds party charts. What do you think?

[mykhailo-sindieiev]

I think maintaining DB servers in the Directus helm chart is a bit out of scope of the Directus helm chart. That was the reason to rely on the 3rd party charts for DB installation. But I see that bitnami has already migrated images to the legacy repo - https://hub.docker.com/layers/bitnamilegacy/mysql/9.4.0-debian-12-r1/images/sha256-504dbf46c911e124f168d364d2b4abff3ee799968b8c8f35445e6a0a57eda44e and I think we can tune mysql values on our side to point bitnami's legacy repo - https://github.com/bitnami/charts/blob/bfa74fb5cb43be45e0238a6fc4db88ae4dad4f78/bitnami/mysql/values.yaml#L99

Unfortunately, I do not have access to the k8s cluster now to prepare the MR, I will do that early September.

Potentially, we just need to modify "repositiry" and "tag" for every dependency we have and point them to the "legacy" or "bitnamisecure" registries:

• Redis - https://github.com/bitnami/charts/blob/main/bitnami/redis/values.yaml#L117
• Mysql - https://github.com/bitnami/charts/blob/bfa74fb5cb43be45e0238a6fc4db88ae4dad4f78/bitnami/mysql/values.yaml#L100
• Postgresql - https://github.com/bitnami/charts/blob/main/bitnami/postgresql/values.yaml#L124

[invisible1988]

Are there any plans to do something here?

[mykhailo-sindieiev]

Hello, yes, I am going to point postgres and mysql dependencies to bitnamilegacy registry. But I am also happy with all your suggestions you might have

[invisible1988]

Currently, I'm using kustomize to override my images. I was wondering if you would be interested in migrating to these new Helm charts: https://github.com/CloudPirates-io/helm-charts

While they are in an early stage, the company behind them seems trustworthy, in my opinion. I would be happy to help with the migration.

[mykhailo-sindieiev]

I did a release that points dependencies to bitnamilegacy repo.

@invisible1988 thank you for sharing that, definitely worth to take a look