Hi Angelo, if you see the Dockerfile, you would see "Kubenetes membership" files are being added as you need to enable kubernetes membership scheme when it is running in Kubernetes. The WKA scheme is not a good fit for containers.
Yes, you need a central volume only if you have multi tenant story or if you deploy secondary user stores, as these cases it needs some deployment artifacts created at runtime. Cheers, Ruwan A On Fri, Oct 18, 2019 at 2:57 PM Angelo Immediata <[email protected]> wrote: > Hi > I state that I'm pretty newbie in docker architectures and please forgive > me if this is not the correct mailing list where to ask these kind of > questions. > > In my project we are evaluating the WSO2 IS docker image we found here > https://github.com/wso2/docker-is > > We are wondering how manage WSO2 clustering and swarm (or kubernetes) > docker images instances. > > Is it possible to create a WSO2 cluster (pattern 1 and/or pattern 2) in a > docker architecture? > My first impression is that we should share a docker volume where to put > all configuration files, also the hazelcast configuration. The hazelcast > configuration will manage a well know range of IP addresses. All WSO2 IS > belonging to this IP range will be member of this cluster. So when swarm > (or kubernetes) understands that a new WSO2 IS instance is needed, it will > start a new docker image and this image will "auto-magically" be member of > the cluster. > But, as far as I know, between docker containers there can be issues in > UDP. > > Is the scenario I proposed a correct scenario? Is it possible to use WSO2 > IS docker image in this scenario? > > Thank you > Angelo > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
