Hi,
thank you for your post.
We don't support truststore in our Helm chart: in fact, we are using the default JVM trustore provided by the base image of OpenJDK.
I have to admint that internally we consider the Helm chart a way to get KNOWAGE fast but we don't use it for complex deployment: we actually render the Helm chart then we patch the result with Kustomize; I really suggest you to take a look a it.
In your case, if you want to consider a 2-step procedure to deploy and manage your installation you can rely on the common Java environment variable for options, the JAVA_OPTS. You create a trustore on your local machine, mount the truststore somewhere inside the KNOWAGE container and set the JAVA_OPTS like
JAVA_OPTS="-Djavax.net.ssl.trustStore=/home/knowage/trustore -Djavax.net.ssl.trustStorePassword=set-password-here"
With Kustomize, you could reference the original Helm chart on GitHub and apply patches automatically. See:
https://cloud.google.com/anthos-config-management/docs/how-to/use-repo-kustomize-helm?hl=it#render_a_remote_helm_chart
I hope you will consider Kustomize because we use it everyday with great results.