Vitaly, If you are using thick (aka. standard) Ignite clients then go ahead and reuse the same IP Finder. The easiest way is to deploy the app in the same namespace and the IP Finder will work out well.
If the cluster is accessed via thin clients or REST protocol then ensure that the proper port numbers are visible via K8 LoadBalancer or by other means: https://apacheignite.readme.io/docs/amazon-web-services-eks-deployment#section-connecting-from-external-applications - Denis On Wed, Sep 11, 2019 at 1:42 PM vitalys <[email protected]> wrote: > We currently have working installation where our Ignite Server Nodes reside > on the standalone VMs and form a Cluster upon start by using shared > Configuration setup. Our Client application joins Cluster on-demand, loads > data into the Cluster and then kicks-off certain operations on the loaded > data. > > We want to migrate Ignite Cluster Nodes from individual VMs to Kubernetes > and containerize them along the way. So our challenge is to have an > existing > client join the Cluster while Cluster Nodes deployment platform is changed. > > I have some reservations about REST client since we need to load > significant > volumes of data in to the Cluster. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
