Roman, Yes, it shouldn't be required to feed external addresses directly if they are listed in the address resolver. It looks it's inevitable that a special IP finder is required here.
-- Denis On Thu, Apr 5, 2018 at 6:03 PM, Roman Shtykh <[email protected]> wrote: > I have been playing with this for a while, and managed to get an external > client node get into the topology, but it failed to communicate to the > cluster. Some points: > 1. Used TcpDiscoveryKubernetesIpFinder for sever nodes > 2. Exposed pods via NodePort on custom ports (higher than 30000); more > flexible than hostNetwork = True > 3. Created an address resolver for finding and communication SPIs, so that > pods addresses are conveyed to the external client. > 4. Used TcpDiscoveryVmIpFinder for the client to successfully join the > topology. > > Unfortunately, TcpCommunicationSPI fails to connect to the server nodes. > The client has all addresses of the ClusterNode it attempts to connect to, > including internal pods' IP, 127.0.0.1, 0:0:0:0:0:0:0:0 and external IP, > but fails to reach the external IP from the list (see TcpCommunicationSPI. > createTcpClient). Having ClusterNode expose only the address that was > registered by the address resolver might fix it (haven't checked yet) -- > anyway, I think the client should not be provided with and communicate via > internal addresses iff external addresses are provided, should it? > > -- Roman > > > On Thursday, April 5, 2018, 3:33:10 p.m. GMT+9, sid_human < > [email protected]> wrote: > > > Hi > > I had recently come across this similar issue. I have multiple ignite > server > pods up in a cluster and running in 3 - 4 nodes. At the same time, I have > ignite clients that can connect and work perfectly fine if they are running > as pods in these nodes. > > I tried to implement an external client connecting to the ignite server > pods > cluster but no avail. I have followed through the readme.io pages of > kubernetes discovery. Here are the issues I had confronted: > > 1) Setting hostNetwork = True in the yaml configuration of ignite pods is a > network issue because running multiple containers on a node and each > container trying to host the port would send an error. So, I tried running > one container - one node. > 2) I have added a comment IGNITE-4161 > <https://issues.apache.org/jira/browse/IGNITE-4161> with the exact client > configurations which seem to retrieve the server pods IP addresses. But no > connection is made. > > I'm afraid no one has tried this before successfully and no development on > external clients are made as someone had posted in the same Jira- issue. > > Thank you. > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
