Hi all, currently, I'm working on building Kubernetes resources for WSO2 Enterprise Integrator [1].
During this effort, I am attempting to utilize platform independent WSO2 product Docker images [2] when deploying artifacts on Kubernetes platform. Here, we are required to pass on the set of files with configuration changes to the default Docker image file system, into a pod in order to make them available at the container startup. The most straightforward solution provided by Kubernetes platform for this purpose is using ConfigMaps [3]. But it was experienced that it is not possible to build a Kubernetes ConfigMap from a folder recursively [4]. As the set of configuration files that need to be passed into the container is required to maintain the folder structure in this scenario, it was identified that using a persistent storage (containing the files with configuration changes) which could be shared among all the pods running containers from the specific Docker image is the best option to achieve the discussed goal. For this purpose, I tried using dynamic provisioning of persistent volumes [5]. But how can we pre-populate the dynamically provisioned persistent volume with the files with configuration changes? Your help, suggestions and concerns on this matter are highly appreciated. *Note*: Please find this [6] forum discussion I've initiated at Kubernetes Storage Special Interest Group [7]. [1]: https://github.com/wso2/kubernetes-ei [2]: Mail thread with subject "[Architecture] [Deployment] [Containers] An update to WSO2 product Dockerfile generalization" [3]: https://kubernetes-v1-4.github.io/docs/user-guide/configmap/ [4]: https://groups.google.com/forum/#!topic/kubernetes-users/h_FRSr5wW00 [5]: https://kubernetes.io/blog/2017/03/dynamic-provisioning-and-storage-classes-kubernetes [6]: https://groups.google.com/forum/#!topic/kubernetes-sig-storage/qhd2HFd7nbg [7]: https://github.com/kubernetes/community/tree/master/sig-storage -- Yours sincerely, *Chiranga Alwis* Software Engineer | WSO2 *Mobile : *+94775930497 *Email: *[email protected] *LinkedIn: *https://lk.linkedin.com/in/chiranga-alwis-391342a9 *Medium:* https://medium.com/@chirangaalwis <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
