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/10/03 06:51: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=17423636#comment-17423636 ] 

Raymond Wilson commented on IGNITE-15602:
-----------------------------------------

You're welcome :)

I have marked this as fixed in 2.12 as this is the next release train I think. Is this sufficient for it to be included in the 2.12 release?

> 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)