You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Raymond Wilson (Jira)" <ji...@apache.org> on 2021/09/27 20:31:00 UTC
[jira] [Commented] (IGNITE-15602) Add
KubernetesConnectionConfiguration.DiscoveryPort property
[ https://issues.apache.org/jira/browse/IGNITE-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421012#comment-17421012 ]
Raymond Wilson commented on IGNITE-15602:
-----------------------------------------
Sorry, I wrote the original text from the wrong viewpoint, I have amended it.
> 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
> Priority: Minor
>
> 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 items makes the following changes:
> * Adds a DiscoveryPort property to KubernetesConnectionConfiguration
> * Passes that DiscoveryPort configuration value to the KubernetesServiceAddressResolver
--
This message was sent by Atlassian Jira
(v8.3.4#803005)