Stop Using Versioned Bitnami Container Images Before August 28th, 2025 #65
Description
Starting August 28th, all existing Bitnami container images, including older or versioned tags (e.g., 2.50.0, etc.), will be migrated from the public catalog (docker.io/bitnami) to the “Bitnami Legacy” repository (docker.io/bitnamilegacy), where they will no longer receive updates. (see "bitnami/containers#83267")
This script) lists all the images we're using in dev and prod k8s clusters, highlighting which bitnami images need to be substituted before the August 28 cutoff. Results below, along with callouts to specific owners for action items.
Note
This is only a stopgap; we'll need to figure out a longer-term alternative soon, since these legacy images will no longer be updated by bitnami!
How to fix (short-term solution).
Example (for postgresql):
- find repo references:
$ tar -xOzf helm/charts/postgresql-16.7.21.tgz postgresql/README.md \
| grep 'repository.*REPOSITORY_NAME/' \
| awk -F'`' '{print $2, $(NF-1)}'
image.repository REPOSITORY_NAME/postgresql
volumePermissions.image.repository REPOSITORY_NAME/os-shell
metrics.image.repository REPOSITORY_NAME/postgres-exporter- In values.yaml overrides, set
REPOSITORY_NAMEtobitnamilegacyfor those params:
image:
repository: bitnamilegacy/postgresql
volumePermissions:
image:
repository: bitnamilegacy/os-shell
metrics:
image:
repository: bitnamilegacy/postgres-exporter- Also allow "insecure" images (i.e. the bitnami legacy images):
global:
security:
allowInsecureImages: trueCaution
REPEAT FOR ALL SUB-CHARTS!