Are Kubernete's ConfigMaps Writable?
Are Kubernete's ConfigMaps Writable?
Is it possible to directly modify the file mounted by configMap? We have an application that reads a configuration file that was configMap type and the application should able to edit the file and the changes should be persisted if the configMap is shared with other pods and when the pod restarts.
configMap
configMap
configMap
If configMap is not meant for this, then what should we relay on consul to save the configuration?
configMap
consul
2 Answers
2
AFAIK the changes to a ConfigMap will only exist locally in-memory.
That is, changes aren't visible to other pods and on a pod restart the changes will be lost.
ConfigMap
One solution is to use the kubectl binary or the kubernetes API from within the configuring application to recreate the ConfigMap after the configuration changes.
kubectl
ConfigMap
e.g. kubectl apply -f /path/to/updated/config.yaml
kubectl apply -f /path/to/updated/config.yaml
Yes a configmap is not intended to be writeable. If you're interacting with files from a configmap then you could instead put the files in a writeable volume and mount the volume. Or you could, as you suggest, use centralised configuration like consul. Given, that the app is dynamically writing to this data you could consider it state rather than configuration. Then it could be stored in a database. Another option could be a distributed cache such as redis or hazelcast.
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
