GitHub user ashokkumar-srinivas created a discussion: Question: How will Superset handle Bitnami image deprecations (PostgreSQL, Redis, etc.)?
Hello there, With the recent announcement from Bitnami regarding changes to their container image catalog (effective August 28, 2025), many of their images - including those used in Helm charts - will either be moved to a legacy repository (docker.io/bitnamilegacy) or no longer receive updates. Reference: https://github.com/bitnami/containers/issues/83267#issuecomment-3296097823 I noticed that Superset's Docker and/or Helm-based setups often use Bitnami containers for dependencies like PostgreSQL or Redis. For example, when using the bitnami/postgresql image in a containerized deployment or in Helm charts with something like: dependencies: - name: postgresql version: 13.4.4 repository: oci://registry-1.docker.io/bitnamicharts condition: postgresql.enabled - name: redis version: 17.9.4 repository: oci://registry-1.docker.io/bitnamicharts condition: redis.enabled These charts often reference Bitnami container images internally, which might be affected by this deprecation. Some of these images may stop receiving updates or be moved to a legacy repo without security patches. How does the Superset team plan to handle these Bitnami deprecations going forward? Thanks, Ashok Kumar Srinivas GitHub link: https://github.com/apache/superset/discussions/35234 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
