From c3bc46d311f86dca22580896f408a6cb11894cdc Mon Sep 17 00:00:00 2001 From: Bitnami Bot Date: Thu, 2 Apr 2026 18:18:15 +0200 Subject: [PATCH] [bitnami/rabbitmq-cluster-operator] Release 2.20.0-debian-12-r0 (#91973) Signed-off-by: Bitnami Bot --- .../2/debian-12/Dockerfile | 8 +++--- bitnami/rabbitmq-cluster-operator/README.md | 27 ++++++------------- 2 files changed, 12 insertions(+), 23 deletions(-) diff --git a/bitnami/rabbitmq-cluster-operator/2/debian-12/Dockerfile b/bitnami/rabbitmq-cluster-operator/2/debian-12/Dockerfile index 568d5dac7d4d..0b1df6e0452c 100644 --- a/bitnami/rabbitmq-cluster-operator/2/debian-12/Dockerfile +++ b/bitnami/rabbitmq-cluster-operator/2/debian-12/Dockerfile @@ -17,7 +17,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \ DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \ mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \ COMPONENTS=( \ - "rabbitmq-cluster-operator-2.19.2-0-linux-${OS_ARCH}-debian-12" \ + "rabbitmq-cluster-operator-2.20.0-0-linux-${OS_ARCH}-debian-12" \ ) ; \ for COMPONENT in "${COMPONENTS[@]}"; do \ if [ ! -f "${COMPONENT}.tar.gz" ]; then \ @@ -39,18 +39,18 @@ ARG TARGETARCH ENV OS_ARCH="${TARGETARCH:-amd64}" LABEL org.opencontainers.image.base.name="scratch" \ - org.opencontainers.image.created="2026-03-11T12:57:01Z" \ + org.opencontainers.image.created="2026-04-02T16:11:42Z" \ org.opencontainers.image.description="Application packaged by Broadcom, Inc." \ org.opencontainers.image.title="rabbitmq-cluster-operator" \ org.opencontainers.image.vendor="Broadcom, Inc." \ - org.opencontainers.image.version="2.19.2" + org.opencontainers.image.version="2.20.0" COPY rootfs / COPY --from=builder /opt/bitnami/rabbitmq-cluster-operator/.spdx-rabbitmq-cluster-operator.spdx /opt/bitnami/rabbitmq-cluster-operator/.spdx-rabbitmq-cluster-operator.spdx COPY --from=builder /opt/bitnami/rabbitmq-cluster-operator/bin/manager /opt/bitnami/rabbitmq-cluster-operator/bin/manager COPY --from=builder /opt/bitnami/rabbitmq-cluster-operator/licenses /opt/bitnami/rabbitmq-cluster-operator/licenses -ENV APP_VERSION="2.19.2" \ +ENV APP_VERSION="2.20.0" \ BITNAMI_APP_NAME="rabbitmq-cluster-operator" \ IMAGE_REVISION="0" \ PATH="/opt/bitnami/rabbitmq-cluster-operator/bin:$PATH" diff --git a/bitnami/rabbitmq-cluster-operator/README.md b/bitnami/rabbitmq-cluster-operator/README.md index 432a3fe373f1..32eb1e0be581 100644 --- a/bitnami/rabbitmq-cluster-operator/README.md +++ b/bitnami/rabbitmq-cluster-operator/README.md @@ -34,25 +34,7 @@ Learn more about the Bitnami tagging policy and the difference between rolling t ## Get this image -The recommended way to get the Bitnami rabbitmq-cluster-operator Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/rabbitmq-cluster-operator). - -```console -docker pull bitnami/rabbitmq-cluster-operator:latest -``` - -To use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/rabbitmq-cluster-operator/tags/) in the Docker Hub Registry. - -```console -docker pull bitnami/rabbitmq-cluster-operator:[TAG] -``` - -If you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the `docker build` command. Remember to replace the `APP`, `VERSION` and `OPERATING-SYSTEM` path placeholders in the example command below with the correct values. - -```console -git clone https://github.com/bitnami/containers.git -cd bitnami/APP/VERSION/OPERATING-SYSTEM -docker build -t bitnami/APP:latest . -``` +The Bitnami RabbitMQ Cluster Operator Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers. ## Why use a non-root container? @@ -78,6 +60,13 @@ Check the [official RabbitMQ Cluster Operator documentation](https://github.com/ - The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes. +### FIPS configuration in Bitnami Secure Images + +The Bitnami RabbitMQ Cluster Operator Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables: + +- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`. +- `GODEBUG`: controls Go FIPS mode. Use `fips140=only` (restricted), `fips140=on` (relaxed), or `fips140=off` (disabled). + ## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.