From 6374a892cbf9510d7cca1df5cd86a3b2bb707fa4 Mon Sep 17 00:00:00 2001
From: Bitnami Bot <bitnami.bot@broadcom.com>
Date: Wed, 8 Apr 2026 10:48:56 +0200
Subject: [PATCH] [bitnami/rmq-messaging-topology-operator] Release
 1.19.0-debian-12-r1 (#92194)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
---
 .../1/debian-12/Dockerfile                    |  6 ++--
 .../rmq-messaging-topology-operator/README.md | 28 ++++++-------------
 2 files changed, 12 insertions(+), 22 deletions(-)

diff --git a/bitnami/rmq-messaging-topology-operator/1/debian-12/Dockerfile b/bitnami/rmq-messaging-topology-operator/1/debian-12/Dockerfile
index d5bac93a6cab..c36c425cba60 100644
--- a/bitnami/rmq-messaging-topology-operator/1/debian-12/Dockerfile
+++ b/bitnami/rmq-messaging-topology-operator/1/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=( \
-      "rmq-messaging-topology-operator-1.19.0-0-linux-${OS_ARCH}-debian-12" \
+      "rmq-messaging-topology-operator-1.19.0-1-linux-${OS_ARCH}-debian-12" \
     ) ; \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -40,7 +40,7 @@ ARG TARGETARCH
 ENV OS_ARCH="${TARGETARCH:-amd64}"
 
 LABEL org.opencontainers.image.base.name="scratch" \
-      org.opencontainers.image.created="2026-03-13T16:08:57Z" \
+      org.opencontainers.image.created="2026-04-08T08:22:05Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.title="rmq-messaging-topology-operator" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
@@ -53,7 +53,7 @@ COPY --from=builder /opt/bitnami/rmq-messaging-topology-operator/licenses /opt/b
 
 ENV APP_VERSION="1.19.0" \
     BITNAMI_APP_NAME="rmq-messaging-topology-operator" \
-    IMAGE_REVISION="0" \
+    IMAGE_REVISION="1" \
     PATH="/opt/bitnami/rmq-messaging-topology-operator/bin:$PATH"
 
 USER 1001
diff --git a/bitnami/rmq-messaging-topology-operator/README.md b/bitnami/rmq-messaging-topology-operator/README.md
index c42600dc3fdf..9069f287a790 100644
--- a/bitnami/rmq-messaging-topology-operator/README.md
+++ b/bitnami/rmq-messaging-topology-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 rmq-default-credential-updater Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/rmq-default-credential-updater).
-
-```console
-docker pull bitnami/rmq-messaging-topology-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/rmq-messaging-topology-operator/tags/) in the Docker Hub Registry.
-
-```console
-docker pull bitnami/rmq-messaging-topology-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 Messaging Topology Operator Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
 
 ## Why use a non-root container?
 
@@ -78,6 +60,14 @@ Check the [official RabbitMQ Messaging Topology Operator documentation](https://
 
 - 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 Messaging Topology 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 &copy; 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.