<p>My environment is that the ignite client is on kubernetes and the ignite server is running on a normal server.
In such an environment, TCP connections are not allowed from the server to the client.
For this reason, CommunicationSpi(server -> client) cannot be allowed.
What I'm curious about is what issues can occur in situations where Communication Spi is not available?
In this environment, Is there a way to make a CommunicationSpi(server -> client) connection?</p>

Lee Changmyung
<p>To support such a deployment configuration you would need to dance a lot around a network configuration - setting up K8 Services, Ignite AddressResolver, etc. The Ignite community is already aware of this inconvenience and working on an out-of-the-box solution.</p>
<p><strong>Updated</strong></p>
<p>If you run Ignite thick clients in a K8 environment and the servers are on VMs, then you need to enable the <a href="https://www.gridgain.com/docs/latest/developers-guide/clustering/running-client-nodes-behind-nat" rel="nofollow noreferrer"><code>TcpCommunicationSpi.forceClientToServerConnections</code> mode to avoid connectivity issues</a>.</p>
<p>If you run Ignite thin clients then configure just provide IPs of servers as <a href="https://www.gridgain.com/docs/latest/installation-guide/kubernetes/amazon-eks-deployment#connecting-with-thin-clients" rel="nofollow noreferrer">described here.</a></p>
