You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed , the configmap for the file config.json might not be the best option as geocontrib normally generate this file for geocontrib-fronted (dynamically)
So we have to manage the content of this file, can be painfull for migration or adding var env
emptyDir for storing the config.json. This will work only if everything can be configured through environment variables and there is no need to add more "configuration" on top of the existing configuration.
a PVC for storing the config.json. Might not be ideal because it's yet another PVC to manage. But allows for adding more "configuration" on top of the existing configuration.
As discussed , the configmap for the file config.json might not be the best option as geocontrib normally generate this file for geocontrib-fronted (dynamically)
So we have to manage the content of this file, can be painfull for migration or adding var env
it refere to this :
charts-gs/geocontrib/values.yaml
Line 7 in 44d9ace
The text was updated successfully, but these errors were encountered: