Jonathan,
Thanks for the extensive summary.
Personally, I like the manager node approach because it's built in Docker
Swarm and doesn't require 3rd party dependencies. Moreover, it reminds me
the way we supported Kubernetes where Ignite pods request IP addresses from
a Kubernetes master.
Hi Denis,
It seems like one workaround would be to configure the URL to one of the
manager node, and then the Docker API allows to loop over all the nodes net
interfaces :
https://github.com/bitsofinfo/docker-discovery-swarm-service#status. The
problem is it needs to know which node is a manager
Hi Jonathan,
Does Docker Swarm go with any internal services concept that can be used to
share Ignite nodes' IPs? Any other internal thing that can store and share
the IPs?
For instance, Ignite Kubernetes IP finder relies on K8 services to exchange
the IPs on the nodes startup:
Hello everyone,
As adviced by @dsetrakyan, I would like to post one simple suggestion about
Ignite and deployment, in particular container one's like docker. Docker
Swarm allows to simply scale a service by setting the "replicas" parameter
to a positive Integer. However, for lot of clustered
