[ https://issues.apache.org/jira/browse/IGNITE-4161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-4161:
--------------------------------
Issue Type: New Feature (was: Task)
> 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: New Feature
> 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)
|