Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.8.1, 2.10, 2.9.1, 2.11
-
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.
-
Docs Required, Release Notes Required
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
Attachments
Issue Links
- is related to
-
-
- Open
-
- links to
