What prevents you from deploying the application within the same K8 environment as a pod? If the thick client and the servers are within the same network then you won't have any hurdles at all. That's the best approach.
Otherwise, you need to a) expose K8 network if you want to connect from a thick client deployed outside or b) use a thin client that supports only SQL and key-value APIs at the moment. - Denis On Tue, Nov 12, 2019 at 12:07 AM camer314 <cameron.mur...@towerswatson.com> wrote: > I am new to Ignite and am struggling to figure out how to connect my client > application to my Ignite cluster hosted in Azure Kubernetes. > > Effectively I want to remotely connect, that is, I dont want my client > machine to be in the topology, its probably not even in the same country, I > would like to connect (C# or REST) to an Ignite cluster and use both the > cache and compute features. It would seem the only way to do this is via > the > 'thin client' which does not support compute? > > I have heard of 'thick client' nodes which offer full API support but I am > not sure what the requirements are for those. > > So my question is, if i have a C# desktop application (or any other piece > of > code) which i want to connect remotely to a Ignite cluster, like Azure > Kubernetes, to perform cache/compute and without participating in the > cluster, how can i do that? Is it possible? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
