<p>I have an issue when OpenShift project deployed with autoscaler configuration like this:</p>
<ul>
<li>Min Pods = 10</li>
<li>Max Pods = 15</li>
</ul>
<p>I can see that deployer immediately creates 5 pods and <em>TcpDiscoveryKubernetesIpFinder</em> creates not one grid, but multiple grids with same <em>igniteInstanceName</em>.</p>
<p><strong>This issue could be is solved by this workaround</strong></p>
<p>I changed autoscaler configuration to start with ONE pod:</p>
<ul>
<li>Min Pods = 1</li>
<li>Max Pods = 15</li>
</ul>
<p>And then scale up to 10 pods (or replicas=10):</p>
<ul>
<li>Min Pods = 10</li>
<li>Max Pods = 15</li>
</ul>
<p>Looks like <em>TcpDiscoveryKubernetesIpFinder</em> is not locking when it reads data from Kubernetes service that maintains list of IP addresses of all project pods.
So when multiple pods started simultaneously it cause multiple grids creation.
But when there is ONE pod started and grid with this pod created - new autoscaled pods are joining this existing grid.</p>
<p>PS No issues with ports 47100 or 47500, comms and discovery is working.</p>

Valeri Shibaev
<p>OP confirmed in the comment, that the problem is resolved:</p>
<blockquote>
<p>Thank you, let me know when TcpDiscoveryKubernetesIpFinder early adoption fix will be available. For now I've switched my Openshift micro-service IgniteConfiguration#discoverySpi to TcpDiscoveryJdbcIpFinder - which solved this issue (as it has this kind of lock, transactionIsolation=READ_COMMITTED).</p>
</blockquote>
<p>You can read more about <a href="https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/ipfinder/jdbc/TcpDiscoveryJdbcIpFinder.html" rel="nofollow noreferrer">TcpDiscoveryJdbcIpFinder - here</a>.</p>
