Bitnami Licensing Change 2025/Q3

Summary

Starting August 28, 2025, access to ready-to-deploy container images from Bitnami will be restricted unless users opt for a paid plan or compile them independently from source code. This change affects our current use of helm charts and therefore containers sourced from Bitnami.

Background:

  • Community users will have access to a reduced number of hardened images. These images are published only under the “latest” tag and are intended for development purposes.

  • Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), 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.

  • For production workloads and long-term support, users are encouraged to adopt Bitnami Secure Images

Use Cases

Usage of Helm chart and containers sourced from the Bitnami repository (bitnami/thanos).

Proposal

Options and migration paths, needs to be discussed.

Option 1

Migration from Helm repo bitnami/thanos (Use: docker.io/bitnami/thanos:0.39.2-debian-12-r0) to stevehipwell/thanos (Use: quay.io/thanos/thanos:v0.39.2) charts

Pro

  • The project and the images are maintained regularly.

Cons

  • Limited subset of helm template values (54) vs (101), probably not sufficient.
  • We have to verify and adjust our Ansible roles.

Option 2

Switch to original Thanos images and override the bitnami/thanos helm Chart image at install/upgrade time to adjust image.repository and image.tag with Thanos quay.io/thanos/thanos:v0.xx.x

Pro

  • The Thanos project and its Docker images are regularly maintained.
  • Minor adjustments are required

Cons

  • We have to verify and adjust our Ansible roles.

Option 3

Fork and adapt Bitnami Thanos charts and migrate current Bitnami charts and images to a private / public container registry.

Specification

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this section are to be interpreted as described in RFC 2119.

Edited by Daniel Muehne