The current documentation related to how to configure the client outside OpenShift (and also valid for clients inside a Service Mesh (using EnvoyProxy) is imcompleted. The current documentation describes the the following property is needed to avoid getting the network topology:

infinispan.client.hotrod.client_intelligence=BASIC 

However, there is another property needed to complete the process:

infinispan.client.hotrod.topologyUpdates=false

We tested and verified these properties using the Node.js client with an application inside a Service Mesh (that it is basically the same with a client outside of OpenShift), where the connection could not go to the final Pod IP.

This reference is described in the following places:

• https://infinispan.org/blog/2018/08/13/nodejs-client-050-with-improved/

The official documentation references affected are:

• https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html/red_hat_data_grid_for_openshift/hotrod_access#hot_rod_configuration_properties_outside_openshift
• https://access.redhat.com/documentation/en-us/red_hat_data_grid/8.4/html/data_grid_operator_guide/connecting-clients#hotrod-configuration-builder_clients