Hi Folks, As I have experienced so far, using configmaps [1] to do configuration management of a particular deployment profile is much handy and effective than the effort we need to put in doing the same using building per-profile docker images.
When ever we require a configuration update to be done for a particular deployment profile, we can easily change the configuration of the specific file and initiate a rolling update [2] for that particular deployment as follows. For example, in the case of wso2/kubernetes-ei [3] kubectl rolling-update wso2ei-pattern1-integrator-deployment -f new-integrator-deployment.yaml No further burden of the need to build docker images again and again per each change and push them to cluster for a simple configuration change. [1] https://kubernetes.io/docs/tasks/configure-pod-container/configmap [2] https://kubernetes.io/docs/tasks/run-application/rolling-update-replication-controller [3] https://github.com/wso2/kubernetes-ei Cheers, Dilan. *Dilan U. Ariyaratne* Senior Software Engineer WSO2 Inc. <http://wso2.com/> Mobile: +94766405580 <%2B94766405580> lean . enterprise . middleware On Thu, Sep 7, 2017 at 10:57 AM, Pubudu Gunatilaka <pubu...@wso2.com> wrote: > Hi Imesh, > > On Thu, Sep 7, 2017 at 10:44 AM, Imesh Gunaratne <im...@wso2.com> wrote: > >> Hi Pubudu, >> >> On Thu, Sep 7, 2017 at 12:54 AM, Pubudu Gunatilaka <pubu...@wso2.com> >> wrote: >> >>> >>> On Wed, Sep 6, 2017 at 11:06 PM, Imesh Gunaratne <im...@wso2.com> wrote: >>> >>>> >>>> Do we really need to parameterize these? Wouldn't it be better to add >>>> all required folders? May be what we need is the bin, conf and deployment >>>> folders (including sub folders)? >>>> >>>> Without mentioning all the configuration files in the dockerfile[1], we >>> can copy all the content of wso2ei-integrator-conf to wso2ei product >>> folder. In this way, users can dynamically add any configuration file >>> without changing the base docker image.They only need to add a configmap >>> and mount that to the wso2ei-integrator-conf folder. >>> >> >> Are you suggesting to use a single configmap and mount that to a single >> conf folder in the pod and then copy file by file to relevant folders? >> >> > As config maps does not support nested folders we have to use multiple > config maps. Rather than hard coding the folder names in the dockerfile > [1], using a script we can copy all the files within wso2ei-integrator-conf > to wso2ei product folder. As I mentioned before, users will be able to add > any configuration file which resides within the product folder without > adding that in the dockerfile. > > [1] - https://github.com/wso2/kubernetes-ei/blob/master/dockerfi > les/integrator/Dockerfile#L25 > > Thank you! > -- > *Pubudu Gunatilaka* > Committer and PMC Member - Apache Stratos > Senior Software Engineer > WSO2, Inc.: http://wso2.com > mobile : +94774078049 <%2B94772207163> > > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
