[
https://issues.apache.org/jira/browse/IGNITE-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420394#comment-17420394
]
Raymond Wilson commented on IGNITE-15602:
-----------------------------------------
I have a code fix for this issue that I would like to contribute to Ignite.
It's really simple. :)
> Expose 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
>
> KubernetesConnectionConfiguration defines a private property, DiscoveryPort,
> which the Ignite Kubernetes finder can use to locate a grid deployed in
> Kubernetes.
>
> However, the TcpDiscoveryKubernetesIpFinder hard wires the port passed to the
> KubernetesServiceAddressResolver to 0, rather than the DiscoveryPort noted 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.
>
> This work items makes the following changes:
> * Makes the DiscoveryPort property in KubernetesConnectionConfiguration
> public
> * Passes that DiscoveryPort configuration value to the
> KubernetesServiceAddressResolver
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
