[
https://issues.apache.org/jira/browse/IGNITE-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Wilson updated IGNITE-15602:
------------------------------------
Release Note: This patch adds a DiscoveryPort configuration item in the
Kubernetes configuration to allow an Ignite node running on Kubernetes to
target a particular Ignite grid. (was: This patch adds a DiscoveryPort
configuration item in the Kubernetes configuration to allow an Ignite running
on Kubernetes to target a particular Ignite grid.)
> Add KubernetesConnectionConfiguration.DiscoveryPort property
> ------------------------------------------------------------
>
> Key: IGNITE-15602
> URL: https://issues.apache.org/jira/browse/IGNITE-15602
> Project: Ignite
> Issue Type: Improvement
> Components: general
> Affects Versions: 2.8.1, 2.10, 2.9.1, 2.11
> Reporter: Raymond Wilson
> Assignee: Raymond Wilson
> Priority: Minor
> Labels: Kubernetes
> Fix For: 2.12
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The TcpDiscoveryKubernetesIpFinder hard wires the port passed to the
> KubernetesServiceAddressResolver to 0, rather than a configurable
> DiscoveryPort specified in KubernetesConnectionConfiguration. This means if
> there is a client to more than one grid deployed to Kubernetes, that client
> can only see one of the grids due to the port being hard wired to 0 causing
> it to use the default port to locate the grid to join.
>
> KubernetesConnectionConfiguration should define a property, DiscoveryPort,
> which the Ignite Kubernetes finder can use to locate a grid deployed in
> Kubernetes.
> This work item makes the following changes:
> * Adds a DiscoveryPort property to KubernetesConnectionConfiguration
> * Passes that DiscoveryPort configuration value to the
> KubernetesServiceAddressResolver
>
> I have added a related documentation ticket here:
> https://issues.apache.org/jira/browse/IGNITE-15630
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
