[bitnami/janusgraph] Helm Pod start in failure caused by secret not found about charts

[olivierlemee]

I found a solution that allow to go to a next step :

1. I set the nameOverride property into the values.yaml of janusgraph helm definition
2. I start the installation of modules project on Minikube via helm command line
3. I see that error regarding "not found secret" does not appear because now, it's the equals name "knr-system-cassandra" which is defined into the Pod resources with equals name into the initialized janusgraph Pod (found regarding the existing secret object instantiated into the Minikube Secrets)
4. BUT... in the Pod events log, I see the after the "Created" log (message = Created container wait-for-storage) regarding the sub-object spec.initContainers(wait-for-storage), there is a log for "Pulled" cause and the Pod stay permanently into a "Init: 0/1" status (I see conditions where "containers with incomplete status: [wait-for-storage]" like causes for ContainersReady and Read and Initialized types which are in a "false" state
5. So, Pod stay in unready status...

In conclusion, at this step end:

• the secret finding problem is partially resolved by the nameOverride approach
• but the current blocking point is the Janusgraph Pods which stay in "wait-for-storage" status during init containers phase (PodInitializing cause without ready status reached)