ZooKeeper Helm Chart Failure: JAVA_FIPS_MODE unbound variable in libzookeeper.sh

Products

• Bitnami Premium (Bitnami Secure Images)
• Bitnami Secure Images

Issue/Introduction

When deploying the Bitnami ZooKeeper Helm Chart on newer base images (e.g., Photon 5 or Debian 12), the ZooKeeper container fails its Liveness and Readiness probes, leading to a CrashLoopBackOff or constant container restarts.

The kubectl describe pod output shows the following errors:

• Warning Unhealthy: Readiness probe failed: /opt/bitnami/scripts/libzookeeper.sh: line 604: JAVA_FIPS_MODE: unbound variable
• Warning Unhealthy: Liveness probe failed: /opt/bitnami/scripts/libzookeeper.sh: line 604: JAVA_FIPS_MODE: unbound variable

Resolution

1. Adjust FIPS Configuration (Photon 5)

For deployments on Photon 5 base images where FIPS is not required, explicitly set the FIPS mode to "off" in your values.yaml file. This ensures the variable is correctly initialized and the probes can complete.

2. Upgrade Chart Version (Debian 12)

For Debian 12 environments, upgrade the ZooKeeper Helm Chart to version 13.17.0 or later. These versions include the necessary logic to ensure all FIPS-related variables are properly defined for the security scripts.

3. Recommended Stable Version

It is strongly recommended to upgrade to ZooKeeper Helm Chart version 13.18.0 or later to ensure compatibility with all recent OS-level configuration requirements.