alex-plekhanov commented on a change in pull request #8206:
URL: https://github.com/apache/ignite/pull/8206#discussion_r487720713



##########
File path: 
modules/kubernetes/src/main/java/org/apache/ignite/client/ThinClientKubernetesAddressFinder.java
##########
@@ -0,0 +1,55 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *      http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.client;
+
+import java.net.InetAddress;
+import java.util.function.Supplier;
+import 
org.apache.ignite.internal.kubernetes.connection.KubernetesServiceAddressResolver;
+import 
org.apache.ignite.kubernetes.configuration.KubernetesConnectionConfiguration;
+
+/**
+ * Address finder for automatic lookup of Ignite server nodes running in 
Kubernetes environment. All Ignite nodes have
+ * to be deployed as Kubernetes pods in order to be found. Applications and 
Ignite nodes running outside of Kubernetes
+ * will not be able to reach the containerized counterparts.
+ * <p>
+ * The implementation is based on a distinct Kubernetes service. The name of 
the service must be set with
+ * {@code KubernetesConnectionConfiguration}. As for Ignite pods, it's 
recommended to label them in such a way that
+ * the service will target only server nodes.
+ * <p>
+ * The address finder, in its turn, will call this service to retrieve Ignite 
pods IP addresses. The port will be
+ * set later within {@link IgniteClient}. Make sure that all Ignite pods 
occupy a similar ClientConnector port,
+ * otherwise they will not be able to connect each other using this address 
finder.
+ * <p>
+ */
+public class ThinClientKubernetesAddressFinder implements Supplier<String[]> {
+    /** Kubernetes service address resolver. */
+    private final KubernetesServiceAddressResolver resolver;
+
+    /** Constructor */
+    public ThinClientKubernetesAddressFinder(KubernetesConnectionConfiguration 
cfg) {
+        resolver = new KubernetesServiceAddressResolver(cfg);
+    }
+
+    /** {@inheritDoc} */
+    @Override public String[] get() {
+        return resolver
+            .getServiceAddresses()
+            .stream().map(InetAddress::getHostAddress)
+            .toArray(String[]::new);

Review comment:
       There will be 100 holders created for each host (and there will be 100 
retries to connect for each host) if port is not set explicitly (see 
ReliableChannel#parseAddresses). Can we also add ports to this array?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to