client node connects to server nodes behind NAT

Hi, Is that possible for a non-Kubernetes client node connects to server nodes within Kubernetes ?  have read below docs seems impossible  https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment#connecting-client-nodes Have tried with thin client outside of Kubernetes

Re: "Failed to update store" cacheCriticalSize

Hi Mike. In your case try one of two ways. In cache configuration: 1. Increase writeBehindFlushSize parameter (default is 10240 bytes). or 2. Decrease writeBehindFlushFreq parameter (default is 5000 ms). https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/CacheConfig

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 client is part of topology, and it has to be able to connect every node in the cluster directly, then thick clients have to be run within the same kubernetes cluster. Thin clients were designed