From baeb952db2922f31d17e4f93513152220faf3fdf Mon Sep 17 00:00:00 2001
From: Bitnami Bot <bitnami.bot@broadcom.com>
Date: Fri, 24 Apr 2026 17:03:25 +0200
Subject: [PATCH] [bitnami/haproxy] Release 3.2.16-debian-12-r0 (#92639)

Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
---
 bitnami/haproxy/3.2/debian-12/Dockerfile | 10 +++++-----
 bitnami/haproxy/README.md                | 12 ++++++++----
 2 files changed, 13 insertions(+), 9 deletions(-)

diff --git a/bitnami/haproxy/3.2/debian-12/Dockerfile b/bitnami/haproxy/3.2/debian-12/Dockerfile
index 65c8740ac717..230a61eb9b2a 100644
--- a/bitnami/haproxy/3.2/debian-12/Dockerfile
+++ b/bitnami/haproxy/3.2/debian-12/Dockerfile
@@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
 ARG TARGETARCH
 
 LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
-      org.opencontainers.image.created="2026-04-08T02:50:52Z" \
+      org.opencontainers.image.created="2026-04-24T14:54:10Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/haproxy/README.md" \
       org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/haproxy" \
       org.opencontainers.image.title="haproxy" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
-      org.opencontainers.image.version="3.2.15"
+      org.opencontainers.image.version="3.2.16"
 
 ENV HOME="/" \
     OS_ARCH="${TARGETARCH:-amd64}" \
@@ -28,7 +28,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=( \
-      "haproxy-3.2.15-2-linux-${OS_ARCH}-debian-12" \
+      "haproxy-3.2.16-0-linux-${OS_ARCH}-debian-12" \
     ) ; \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -45,9 +45,9 @@ RUN chmod g+rwX /opt/bitnami
 RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
 RUN uninstall_packages curl
 
-ENV APP_VERSION="3.2.15" \
+ENV APP_VERSION="3.2.16" \
     BITNAMI_APP_NAME="haproxy" \
-    IMAGE_REVISION="2" \
+    IMAGE_REVISION="0" \
     PATH="/opt/bitnami/haproxy/sbin:/opt/bitnami/haproxy-dataplaneapi/bin:/opt/bitnami/lua/bin:$PATH"
 
 USER 1001
diff --git a/bitnami/haproxy/README.md b/bitnami/haproxy/README.md
index 4dfc0e24c189..77c48e936fef 100644
--- a/bitnami/haproxy/README.md
+++ b/bitnami/haproxy/README.md
@@ -11,6 +11,14 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
 docker run --name haproxy bitnami/haproxy:latest
 ```
 
+## Using `docker-compose.yml`
+
+The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
+
+[https://github.com/bitnami/containers/tree/main/bitnami/haproxy/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/haproxy/docker-compose.yml)
+
+Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/haproxy).
+
 ## Why use Bitnami Secure Images?
 
 Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@@ -36,10 +44,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
 
 The Bitnami HAProxy Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
 
-## Using `docker-compose.yaml`
-
-Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/haproxy).
-
 ## Why use a non-root container?
 
 Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers [in our docs](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-work-with-non-root-containers-index.html).