search

Ontotext-AD / graphdb-helm

Official Helm chart for GraphDB
https://www.ontotext.com/products/graphdb/
Apache License 2.0
15 stars 18 forks source link

Provide a way of mounting configmaps in the node pod instead of copying them to a file in the node's FS #47

Open mlkiefer opened 1 year ago

mlkiefer commented 1 year ago

Hi,

I'm using the helm chart for running a graphdb instance, installation happens via terraform in a CI/CD system. I've created a configMap for the graphdb.properties and was confused to see that changes in that configMap never reach the graphdb pod. The reason is that this configMap is only being used in the init container. If the configMap does not exist in the pod's filesystem, it is created by copying it from the configMap. I'd like to keep the content of graphdb.properties in my git and have the CI/CD system take care of changes in a clean way. Therefore, I'd like to have a way of directly mounting this configMap in the pod that runs graphdb. The current way of only copying it once seems very intransparent to me...

Best regards, Michael Kiefer

farhan-ejaz commented 1 year ago

completely back this issue. The graphdb.properties file is mounted on the pv at /opt/graphdb. It would be better it is mounted on the pod filesystem so that it can be updated. Somehow the init container is not replacing the files on the pv fs

Sukhumi commented 1 year ago

Because of issues in the past with some cloud providers when mounting 1 file in multiple pods at the same time we've currently done it with the init container. With the latest 10.2.1 release the init container should now replace the graphdb.properties file.