[
https://issues.apache.org/jira/browse/IGNITE-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879955#comment-15879955
]
Denis Magda commented on IGNITE-4161:
-------------------------------------
In general, we might not need to develop one more IP finder for the nodes
connecting outside of Kubernetes if the following works out:
* Set hostNetwork=true in Ignite pod's YAML configuration so that the nodes
that will be connecting from outside can establish TCP/IP connections with
containerized Ignite nodes (pods).
* Use the same TcpDiscoveryKubernetesIpFinder for the nodes that will be
outside of Kubernetes environment.
Needs to be checked in a Kubernetes on-premise or cloud environment.
> 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
> Affects Versions: 2.0
> Reporter: Denis Magda
> Fix For: 2.0
>
>
> 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
(v6.3.15#6346)
