Re client node connects to server nodes behind NAT

[MJ]

That would be peer class loading && data stream . 


Thanks


------------------ ???????? ------------------
??????:                                                                         
                                               "user"                           
                                                         
<timonin.ma...@gmail.com&gt;;
????????:&nbsp;2021??11??15??(??????) ????3:59
??????:&nbsp;"user"<user@ignite.apache.org&gt;;

????:&nbsp;Re: client node connects to server nodes behind NAT



Hi, I'll touch on a similar topic a little tomorrow on IgniteSummit [1], you're 
welcome :)

But, a thick&nbsp;client&nbsp;is part of topology, and it has to be able to 
connect every node in the cluster directly, then thick clients have to&nbsp;be 
run within the same kubernetes cluster. Thin clients were designed to eliminate 
this&nbsp;problem.


What features of thick clients do you want to use?


[1]&nbsp;https://ignite-summit.org/sessions/293596



On Mon, Nov 15, 2021 at 3:50 AM MJ <6733...@qq.com&gt; wrote:

Hi,


Is that possible for a non-Kubernetes&nbsp;client node connects to server nodes 
within Kubernetes&nbsp;?&nbsp;


have read below docs seems impossible&nbsp;
https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment#connecting-client-nodes



Have tried with thin client outside of Kubernetes - that works fine
client node(thick client) - always throw exceptions, most likely the internal 
ips bebind NAT cannot be detected from external , is there any workaround to 
implement that non-Kubernetes&nbsp;client node connects to server nodes within 
Kubernetes ? I'd like to utilise the power features of thick client. and They 
can be depoloyed everywhere if there is the way of making it.&nbsp;






Thanks,
Ma Jun