Here is where random ports come from, both ServerImpl and ClientImpl ask TcpDiscoverySpi to get socket, and it's implemented as `sock.bind(new InetSocketAddress(locHost, 0));`
https://github.com/apache/ignite/blob/2.6.0/modules/core/src/main/java/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.java#L1471 I'm sure it's fine in general, because, well, that's how you get a client socket, but I'm not sure if that plays well with Kubernetes given how strict it is about container ports, I do however expect k8s to only require ingress ports to be exposed explicitly -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
