diff --git a/bitnami/kserve-controller/0/debian-12/Dockerfile b/bitnami/kserve-controller/0/debian-12/Dockerfile
index f7e2e0ada6d2..40f55a393061 100644
--- a/bitnami/kserve-controller/0/debian-12/Dockerfile
+++ b/bitnami/kserve-controller/0/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=( \
-      "kserve-0.17.0-0-linux-${OS_ARCH}-debian-12" \
+      "kserve-0.17.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-14T01:15:57Z" \
+      org.opencontainers.image.created="2026-04-08T04:08:14Z" \
       org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
       org.opencontainers.image.title="kserve-controller" \
       org.opencontainers.image.vendor="Broadcom, Inc." \
@@ -51,7 +51,7 @@ COPY --from=builder /opt/bitnami/kserve /opt/bitnami/kserve
 
 ENV APP_VERSION="0.17.0" \
     BITNAMI_APP_NAME="kserve-controller" \
-    IMAGE_REVISION="0" \
+    IMAGE_REVISION="1" \
     PATH="/opt/bitnami/kserve/bin:$PATH"
 
 USER 1001
diff --git a/bitnami/kserve-controller/README.md b/bitnami/kserve-controller/README.md
index a961eb12a4f9..ac076cf0e0b6 100644
--- a/bitnami/kserve-controller/README.md
+++ b/bitnami/kserve-controller/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 KServe Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/kserve-controller).
-
-```console
-docker pull bitnami/kserve-controller: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/kserve-controller/tags/) in the Docker Hub Registry.
-
-```console
-docker pull bitnami/kserve-controller:[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 KServe Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
 
 ## Why use a non-root container?
 
@@ -72,6 +54,14 @@ docker run --rm --name kserve-controller bitnami/kserve-controller:latest --  --
 
 Check the [official KServe documentation](https://kserve.github.io/website) for more information.
 
+
+### FIPS configuration in Bitnami Secure Images
+
+The Bitnami KServe 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.