setting baseline topology in kubernetes

[arunkjn <ar...@gmail.com>]

Hi,

We run a ignite cluster in kubernetes. We currently deploy our containerised
java code which uses xml to configure ignite nodes and start them. We use
Kubernetes Discovery for service discovery.

I want to do automatic cluster activation by defining baseline topology
using control.sh script as described in the docs. I am not able to
understand how to configure control.sh to use kubernetes service discovery
to connect to my running nodes?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: setting baseline topology in kubernetes

[aealexsandrov <ae...@gmail.com>]

Hi,

No 11211 is a default ignite TCP port. For every new node, it will be
incremented 11211, 11212, 11213, etc.

Also please check that you didn't overwrite it. 

https://www.gridgain.com/sdk/pe/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html#setLocalPort-int-

And yes ignite TCP port should be exposed for every node in case if you are
going to work with them from outside.

BR,
Andrei



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: setting baseline topology in kubernetes

[arunkjn <ar...@gmail.com>]

Hi Alex,

It accepts an IP and port as an argument. Do I need to enable ignite rest
and expose rest endpoints on cluster nodes for this to work?

Thanks,
Arun



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: setting baseline topology in kubernetes

[aealexsandrov <ae...@gmail.com>]

Hi,

All existing options of control.sh tool you can see here:

https://apacheignite.readme.io/docs/baseline-topology#section-cluster-activation-tool

To connect to some host and port you can use --host --port options (default
values 127.0.0.1 and 11211). 

In case if you started the ignite in some container then you can use
control.sh from the container or you can expose required ports outside of
your container and connect to it.

BR,
Andrei 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/