Thanks Humphrey, yes, finally I migrate the test to a multinode kubernetes with several pods and the same configuration worked fine. If the visor is started on a pod (inside the grid) the configuration adobe works as the Visor only needs to be connected to one component inside the grid. What I dont have clear is why TcpDiscoveryKubernetesIpFinder doesnt work with Visor ... but anyway, the cluster is running.
El jue., 14 nov. 2019 a las 21:47, Humphrey (<[email protected]>) escribió: > We did the same, creating a pod with the following configuration: > > > And then we point to the visor command (startvisor.sh) where we pass the > config file: > > > In the environment, we are passing the project name, I think in your case > you're using default namespace, so you can put there default. We have > packaged all the dependend jars and put it in a lib folder. > > When the container starts it needs to keep running and then we enter the > console and start up visor from there. When we done we can close visor and > stop the pod. > > Humphrey > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
