Hi Knox Dev Team, I am working on deploying Apache Knox in a Kubernetes (K8s) environment and have encountered a few issues with the current apache/knox:latest Docker image. I wanted to check whether others have seen similar problems and whether there are recommended resolutions.
Environment: Kubernetes-based deployment Using Docker image: apache/knox:latest Issues observed: Issue #1 – keytool path in entrypoint script The entrypoint.sh script refers to the keytool utility using a fixed path (/usr/bin/keytool). However, in the container environment, the Java keytool is located in a different directory and not under /usr/bin. This causes failures during initialization. Issue #2 – Keystore password length The password used to protect the keystore files appears to be too short (default appears to match MASTER_SECRET). This causes the keytool utility to fail during keystore generation due to password length requirements. While investigating and attempting to fix the above issues directly from the source repository, I encountered an additional concern: Issue #3 – Base image accessibility The Docker build references the base image: dhi.io/eclipse-temurin:17-jdk-debian13-dev I was unable to access this image. Is there a specific reason for using this base image instead of the standard: eclipse-temurin:17-jdk If others have encountered similar issues while running Knox in Kubernetes, I would appreciate any guidance or recommended fixes. If these are confirmed issues, I would be happy to contribute patches to address them. Thanks, Selva
