[
https://issues.apache.org/jira/browse/IGNITE-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415184#comment-16415184
]
Siddarth sreeni commented on IGNITE-4161:
-----------------------------------------
I tried what you have said by setting hostNetwork: True. Following I have set
the following to the external client side
{code:java}
TcpDiscoverySpi spi = new TcpDiscoverySpi();
TcpDiscoveryKubernetesIpFinder ipFinder = new
TcpDiscoveryKubernetesIpFinder();
ipFinder.setMasterUrl("https://XXXX.us-east-1.elb.amazonaws.com";);
ipFinder.setAccountToken("path\to\token");
spi.setIpFinder(ipFinder);
IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setDiscoverySpi(spi);
Ignition.setClientMode(true);
ignite = Ignition.start(cfg);
{code}
This works well and returns the host IP address of the ignite servers, although
no connection is established between the client and the server. I have followed
the tutorial given on the readme.io documentation of apache ignite kubernete
deployment http method.
Note: Launching multiple pods on the same node will give an error as both
containers are trying to listen on the same host port. I have only deployed one
ignite server pod.
These are the logs that returned.
{code:java}
WARNING: Failed to connect to any address from IP finder (will retry to join
topology every 2 secs): [/x.x.x.x:47500]
[13:27:54] Failed to connect to any address from IP finder (will retry to join
topology every 2 secs): [/x.x.x.x:47500]
WARNING: Failed to connect to any address from IP finder (will retry to join
topology every 2 secs): [/x.x.x.x:47500]
[13:33:03] Failed to connect to any address from IP finder (will retry to join
topology every 2 secs): [/x.x.x.x:47500]
{code}
> Discovery SPI for nodes that will connect to Ignite Kubernetes cluster from
> outside
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-4161
> URL: https://issues.apache.org/jira/browse/IGNITE-4161
> Project: Ignite
> Issue Type: Sub-task
> Components: general
> Affects Versions: 2.0
> Reporter: Denis Magda
> Priority: Major
>
> Ignite cluster can be considered as a set of Kubernetes pods of a similar
> type that are scaled across available hardware. To get access to the cluster
> from outside the one has to use Kubernetes Service that will expose a single
> public API address for the whole Ignite Cluster.
> Let's think over how an Ignite client can connect to the Ignite's Kubernetes
> cluster from outside, look up nodes and interact with them. As a result, most
> likely we will implement a special discovery SPI for such "outside" nodes
> that will connect to Kubernetes Service before the joining process.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
