Re: Kubernetes - Access Ignite Cluster Externally

Roman, I know this is old, but thanks for your summary. I was able to get your method to work, but with an additional step in the config. It seems that if localAddress is not set via config, that ignite will enumerate all interfaces (of which there are ususally more than one for docker

Re: Kubernetes - Access Ignite Cluster Externally

Roman, Yes, it shouldn't be required to feed external addresses directly if they are listed in the address resolver. It looks it's inevitable that a special IP finder is required here. -- Denis On Thu, Apr 5, 2018 at 6:03 PM, Roman Shtykh wrote: > I have been playing with

Re: Kubernetes - Access Ignite Cluster Externally

Hello Ryan, Astonishing. Thanks for contributing this step-by-step guidance! We'll prepare a special documentation page for that: https://issues.apache.org/jira/browse/IGNITE-6241 -- Denis On Fri, Apr 6, 2018 at 6:17 AM, Ryan Samo wrote: > Denis, > Sorry for the late reply

Re: Kubernetes - Access Ignite Cluster Externally

Denis, Sorry for the late reply as I have been away from a computer for a few days. Today, I do not use Kubernetes in production, it is only in use for POC work so that I can understand how to utilize the K8s platform and test if it works well with Ignite. So far, Ignite seems to be playing nicely

Re: Kubernetes - Access Ignite Cluster Externally

I have been playing with this for a while, and managed to get an external client node get into the topology, but it failed to communicate to the cluster. Some points:1. Used TcpDiscoveryKubernetesIpFinder for sever nodes 2. Exposed pods via NodePort on custom ports (higher than 3); more

Re: Kubernetes - Access Ignite Cluster Externally

Hi I had recently come across this similar issue. I have multiple ignite server pods up in a cluster and running in 3 - 4 nodes. At the same time, I have ignite clients that can connect and work perfectly fine if they are running as pods in these nodes. I tried to implement an external client

Re: Kubernetes - Access Ignite Cluster Externally

Hi Ryan, I see you've already come across the ticket that intended to bring the capability of connecting Ignite nodes that are both inside and outside Kubernetes: https://issues.apache.org/jira/browse/IGNITE-4161 As you see, there is no progress for now, and I'll appreciate if you take over the

Re: Kubernetes - Access Ignite Cluster Externally

Ok thank you all for the tips, I will give it a try! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Kubernetes - Access Ignite Cluster Externally

To access ignite from outside of kubernetes, you need to enable hostNetwork in the kubernetes cluster for your ignite server pods (this is not enabled with default permissions as it goes against many of the core principals of kubernetes). This will allow the ignite server to attach directly

Re: Kubernetes - Access Ignite Cluster Externally

Hello Ryan! I might be terribly wrong, but my first guess is, you should use TcpDiscoveryKubernetesIpFinder for Server nodes inside container, and TcpDiscoveryVmIpFinder for outside client nodes. If you're reaching for setAddresses(), that's the one you should take. With regards to breakage,

Kubernetes - Access Ignite Cluster Externally

Hey guys and gals! I have created a development environment for Ignite 2.3 Native Persistence on Kubernetes 1.9.3 and have it up and running successfully. I then attempted to activate one of my clusters via a Java client call and discovered that the TcpDiscoveryKubernetesIpFinder doesn't support