Problem
This repository currently relies on Bitnami Helm charts (notably Keycloak and MongoDB). Bitnami has changed how their public artifacts are distributed, and “legacy” artifacts are not expected to receive updates. For downstream users, this creates risk around:
- Long-term availability of pinned versions/tags
- Security updates / CVE patching if forced onto legacy artifacts
- Potential cost/plan requirements depending on how Bitnami artifacts are accessed
This makes Bitnami a brittle dependency for foundational components like Keycloak and MongoDB.
References:
Where it affects this repository
Possible resolution (high-level)
Replace Bitnami chart dependencies with community-maintained alternatives, e.g.:
This would remove the Bitnami dependency and reduce the risk of relying on legacy/unpatched artifacts.
Ask
Are maintainers considering to migrating these dependencies away from Bitnami? If yes, this would sustain long-term support of the basyx helm charts. Otherwise, they will quickly be outdated and unusable.
Problem
This repository currently relies on Bitnami Helm charts (notably Keycloak and MongoDB). Bitnami has changed how their public artifacts are distributed, and “legacy” artifacts are not expected to receive updates. For downstream users, this creates risk around:
This makes Bitnami a brittle dependency for foundational components like Keycloak and MongoDB.
References:
Where it affects this repository
Possible resolution (high-level)
Replace Bitnami chart dependencies with community-maintained alternatives, e.g.:
This would remove the Bitnami dependency and reduce the risk of relying on legacy/unpatched artifacts.
Ask
Are maintainers considering to migrating these dependencies away from Bitnami? If yes, this would sustain long-term support of the basyx helm charts. Otherwise, they will quickly be outdated and unusable.