Many Kubernetes platforms were built on free Bitnami images and charts. That catalogue is gone from Docker Hub. We find every Bitnami reference in your stack, stop the immediate risk, and move each component to an image and chart you control — built, scanned and updated in your own pipeline.
Bitnami's free catalogue left Docker Hub; the legacy copies get no security updates.1
Find every Bitnami reference, mirror what you run today, then replace component by component.
Images and charts you control, rebuilt and scanned in your GitLab CI.
docker.io/bitnami/… or bitnamilegacy images.From the Bitnami announcement on the Broadcom community site:1
docker.io/bitnami catalogue (after a postponement).There is no single answer. We pick per component and explain why.
| Option | When it fits | What you maintain |
|---|---|---|
| Official upstream image and chart | The project publishes and maintains its own image and chart | Version upgrades only |
| Kubernetes operator | Stateful services such as databases, where an operator handles backups and failover | The operator and its custom resources |
| Your own image from a minimal base | No good upstream image, or you need a hardened build | A small Dockerfile, rebuilt and scanned automatically in GitLab CI |
| Bitnami subscription | Many components, little time, and the price works for you | Nothing — but you pay per year |
Every Bitnami image and chart in manifests, Helm values, CI files and running clusters — with the version and who owns it.
Images you run today copied into your own registry in the first days, so nothing breaks while we work.
Chosen option, tested in a non-production environment, values and data migrated where needed.
Base images built in GitLab CI, scanned for vulnerabilities, with an SBOM, rebuilt on a schedule.
New versions show up as merge requests, so upgrades are reviewed instead of forgotten.
How to add an image, react to a critical vulnerability, upgrade a chart.
The order is always the same. How long each step takes depends on your volume — the measurement in step 1 sets the price and the dates. Our free scope script gives the first numbers.
Find every reference; mirror running images into your registry; agree the option per component and the final price.
Build or adopt replacements, test them, migrate data for stateful services in agreed windows.
Image pipeline and update flow running; runbook and session with your team.
Fixed price after the measurement in step 1. Paid by milestone.
It keeps things running, but those images get no security updates. Treat it as a short bridge and plan the move.
Sometimes that is the right answer. We put both options next to each other with your numbers and you decide.
With an official chart, values often need changes. We translate them and test the result before touching production.
For stateful services we plan the move per service: backup, restore or replication, and a tested rollback.
Or let us find them. A 30-minute call is enough to estimate the work.