Two hundred charts pointing at a frozen registry
A SaaS platform team repointed every Bitnami chart to bitnamilegacy in August 2025 to stop ImagePullBackOff errors. A year later, the images are still running, unpatched, across dozens of clusters.
Challenge
The official images use different variables, data paths and users, so switching means rewriting charts and risking stateful workloads. Several databases run versions that are past end of life, which no free image covers.
Environment
Kubernetes clusters running Bitnami charts for PostgreSQL 13, Redis 7.2, Kafka 3.x and RabbitMQ 3.13, all on bitnamilegacy images.
Approach
OSSeva inventories every Bitnami reference, ships patched Bitnami-compatible images including the EOL versions, and repoints charts with a values override, stateless workloads first.
What this delivers
Maintained images behind the same charts, with SBOMs for every image and no data-path migrations.