Home›Services›Bitnami exit

Stop depending on Bitnami images you no longer get updates for

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.

from $4,000 · fixed price Measured first, then fixed price and dates No surprise outages from missing images
The problem

Bitnami's free catalogue left Docker Hub; the legacy copies get no security updates.1

What we do

Find every Bitnami reference, mirror what you run today, then replace component by component.

The result

Images and charts you control, rebuilt and scanned in your GitLab CI.

Is this you?

What changed

From the Bitnami announcement on the Broadcom community site:1

How we replace each component

There is no single answer. We pick per component and explain why.

OptionWhen it fitsWhat you maintain
Official upstream image and chartThe project publishes and maintains its own image and chartVersion upgrades only
Kubernetes operatorStateful services such as databases, where an operator handles backups and failoverThe operator and its custom resources
Your own image from a minimal baseNo good upstream image, or you need a hardened buildA small Dockerfile, rebuilt and scanned automatically in GitLab CI
Bitnami subscriptionMany components, little time, and the price works for youNothing — but you pay per year

What you get

Full inventory

Every Bitnami image and chart in manifests, Helm values, CI files and running clusters — with the version and who owns it.

Immediate safety net

Images you run today copied into your own registry in the first days, so nothing breaks while we work.

Replacement per component

Chosen option, tested in a non-production environment, values and data migrated where needed.

Image pipeline

Base images built in GitLab CI, scanned for vulnerabilities, with an SBOM, rebuilt on a schedule.

Update flow

New versions show up as merge requests, so upgrades are reviewed instead of forgotten.

Runbook

How to add an image, react to a critical vulnerability, upgrade a chart.

How it goes

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.

  1. Step 1 · 1–3 days

    Inventory and safety net

    Find every reference; mirror running images into your registry; agree the option per component and the final price.

  2. Step 2

    Replace

    Build or adopt replacements, test them, migrate data for stateful services in agreed windows.

  3. Step 3

    Automate and hand over

    Image pipeline and update flow running; runbook and session with your team.

What we need from you

  • Read access to repositories with manifests and Helm values.
  • Access to a non-production cluster for testing.
  • A registry we can push images to (or we set one up).
  • Change windows for stateful services.

Not included

  • Upgrading your applications themselves.
  • Major version upgrades of databases beyond what the move needs — we flag and quote them.
  • Running the image pipeline for you after handover — see Open-stack care.
from $4,000

Fixed price after the measurement in step 1. Paid by milestone.

What changes the price

  • Number of components using Bitnami images or charts.
  • Stateful services — databases and queues take more care than stateless ones.
  • Clusters and environments to update.

Questions teams ask

We pinned bitnamilegacy tags. Is that fine for now?

It keeps things running, but those images get no security updates. Treat it as a short bridge and plan the move.

Should we just buy the Bitnami subscription?

Sometimes that is the right answer. We put both options next to each other with your numbers and you decide.

Will our Helm values still work?

With an official chart, values often need changes. We translate them and test the result before touching production.

What about data in our databases?

For stateful services we plan the move per service: backup, restore or replication, and a tested rollback.

Often done together

Send us your list of Bitnami images

Or let us find them. A 30-minute call is enough to estimate the work.

Pick a 30-minute slot Opens our booking calendar in a new tab · or write to info@dvs.hk
Sources — public announcements, documentation and legal texts, for orientation only; not legal advice. Bitnami is a trademark of Broadcom.
  1. Broadcom Community: How to prepare for the Bitnami changes (Aug 18, 2025)
Book a 30-minute call