[
https://issues.apache.org/jira/browse/IGNITE-22942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878760#comment-17878760
]
Roman Puchkovskiy edited comment on IGNITE-22942 at 9/3/24 7:52 AM:
--------------------------------------------------------------------
Now, if a name (not an address) is provided in the original list, it's being
resolved to addresses. If it resolves to none, it just contributes nothing to
the output. If it resolves to more than one address, all of them are included
in the result.
This will allow StaticNodeFinder to be more useful in Kubernetes environments.
was (Author: rpuch):
Now, if a name (not an address) is provided in the original list, it's being
resolved to addresses. If it resolves to none, it just contributes nothing to
the output. If it resolves to more than one address, all of them are included
in the result.
This will allow `StaticNodeFinder` to be more useful in Kubernetes environments.
> NodeFinder should be able to resolve multiple IP addresses under the same
> host name
> -----------------------------------------------------------------------------------
>
> Key: IGNITE-22942
> URL: https://issues.apache.org/jira/browse/IGNITE-22942
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr Polovtsev
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> It would be useful to have a NodeFinder that will be able to resolve multiple
> IP addresses that are hidden behind a single host name. This is required to
> better target Kubernetes with its [Headless
> Services|https://kubernetes.io/docs/concepts/services-networking/service/#headless-services].
> As a solution we may provide either a new NodeFinder implementation that will
> resolve such addresses, or augment the StaticNodeFinder's behavior. The
> latter is preferable from the UX POV.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
