Migrate Helm Charts (for 25.09) from Bitnami to BitnamiLegacy Repository

[stephanbcbauer]

Overview

The official Bitnami Helm chart repository has been deprecated or is no longer maintained in its previous location. Bitnami has migrated legacy container images to a new repository called bitnamilegacy. Helm charts using Bitnami container images must be updated to reference this new source to ensure continued functionality. With bitnamilegacy we won’t receive security updates. After release 25.09 we need to carefully evaluate the implications.

Please see here an example pull request.

Explain the topic in 2 sentences

We need to update all Helm charts that use Bitnami container images to point to bitnamilegacy. This ensures stability of deployments while acknowledging that future security updates will not be provided.

What's the benefit?

• Ensures existing Helm charts continue to work after Bitnami’s migration.
• Reduces risk of broken deployments due to missing container images.
• Provides a clear migration path and documentation for maintainers.

What are the Risks/Dependencies ?

• Risk: No future security updates from BitnamiLegacy.
• Dependency: Each chart must be verified for overrides in values.yaml (e.g., keycloak, postgresql).
• May require coordination with multiple repositories using Bitnami dependencies.
• Requires committers of each chart to increment patch versions and test.

Detailed explanation

Current implementation

Helm charts currently rely on the official Bitnami container image repository. That repository is no longer maintained in the same location.

Proposed improvements

• Override the container image repository in Helm chart dependencies from bitnami/... to bitnamilegacy/....
• Increase patch version in Chart.yaml to reflect maintenance changes.
• Document migration and risks in release notes/changelogs.
• Test charts in integration environments to confirm compatibility.

Feature Team

See the Affected teams/products at the bottom

User Stories

• Update all Tractus-X Helm charts to use bitnamilegacy images (repo links per chart).
• Test and validate functionality in integration environments (app-dashboard).
• Provide changelog/release note entry describing the migration.

Acceptance Criteria

• All Helm charts using Bitnami images have been updated to bitnamilegacy.
• Chart patch versions have been incremented.
• Integration tests pass with new images.
• Release notes/changelog entries created.
• Example PR references included (e.g. puris#956).

Manual

PLEASE BE WARE to follow the steps for every image which is related to bitnami ... postgre, keycloak ... and others?

Override container image

Steps

1. Open values.yaml of chart (e.g. postgresql).
2. Override image.repository and image.tag to point to bitnamilegacy.
3. Run helm install or helm upgrade in test environment.

Expected Result

• Chart installs successfully.
• Pod uses bitnamilegacy/postgresql:<tag> image.

Patch version increment

Steps

1. Edit Chart.yaml version from x.y.z to x.y.(z+1).
2. Run helm lint and helm dependency update.

Expected Result

• Version bump is detected.
• Chart passes linting and builds.

Documentation

Steps

1. Add changelog entry with migration note.
2. Commit and push.

Affected teams/products

Please create an issue on your product sepcific repository and link it to the parent (this) issue. PLease tick the checkbox, if you have done the changes and everything works as expected ;) Thx

• Portal — @typecastcloud
• Portal-IAM — @typecastcloud
• BPDM — @nicoprow
• Policy Hub — @typecastcloud
• SSI-Authority-Schema-Registry — @Phil91 , @typecastcloud
• SSI-Credential-Issuer — @Phil91 , @typecastcloud
• SLDT Digital Twin Registry — @agg3fe
• bpn-did-resolution-service (BDRS) — @lgblaumeiser
• EDC (Connector) — @lgblaumeiser
• Industry Core Hub — @matbmoser
• PURIS — @tom-rm-meyer-ISST