[IGNITE-15602] Add KubernetesConnectionConfiguration.DiscoveryPort property

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.8.1, 2.10, 2.9.1, 2.11
• Fix Version/s: 2.12
• Component/s: general
• Labels: Kubernetes
• 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.
• Ignite Flags: Docs Required, Release Notes Required

Language

java

• Assignee: Raymond Wilson
• Reporter: Raymond Wilson
• Reviewer: Pavel Tupitsyn
• Created: 26/Sep/21 21:21
• Updated: 06/Oct/21 00:44
• Resolved: 30/Sep/21 08:29

Description

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

Issue Links

• is related to: IGNITE-15630 Document new KubernetesConnectionConfiguration.DiscoveryPort property
• links to: GitHub Pull Request #9443