You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/04/20 15:28:04 UTC
[jira] [Updated] (IGNITE-4161) Discovery SPI for nodes that will
connect to Ignite Kubernetes cluster from outside
[ https://issues.apache.org/jira/browse/IGNITE-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-4161:
------------------------------------
Fix Version/s: (was: 2.0)
2.1
> 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
> Fix For: 2.1
>
>
> 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)