Its hard to predict all the ways that the chart will be used.
Our named template approach for the fhir config files is pretty flexible, but there are still some cases where a user may want to add a file / set of files to the running ibm-fhir-server container.
One such use case is the ability to add a custom cert for a postgresql database, because the java postgres driver doesn't use the jvm's truststore by default.
Mature charts I've seen expose extraVolumes / extraVolumeMounts values for providing this level of flexibility.
Bitnami charts make these things an array.
The Codecentric keycloak chart makes these string that are evaluated by template.
Personally, I've found the templated strings to be a bit more flexible, so I'm leaning that way at the moment.
Its hard to predict all the ways that the chart will be used. Our named template approach for the fhir config files is pretty flexible, but there are still some cases where a user may want to add a file / set of files to the running ibm-fhir-server container.
One such use case is the ability to add a custom cert for a postgresql database, because the java postgres driver doesn't use the jvm's truststore by default.
Mature charts I've seen expose
extraVolumes
/extraVolumeMounts
values for providing this level of flexibility.Bitnami charts make these things an array. The Codecentric keycloak chart makes these string that are evaluated by template. Personally, I've found the templated strings to be a bit more flexible, so I'm leaning that way at the moment.