anchor.diff:  
   Combined with `bind_port` / `port_range`, the protocol will then send a discovery request to all instances and wait for
   the responses.
  -
  -This is done by superclass `TCPPING` (see  http://www.jgroups.org/manual4/index.html#TCPPING_Prot for details).
   
   A sample configuration looks like this:
   
  
positive.code: [align="left",width="90%",cols="2,10",options="header"]
  |===============
  |Attribute name|Description
  
  |connectTimeout|Max time (in millis) to wait for a connection to the Kubernetes server. If exceeded, an exception
  will be thrown
  
negative.code: On a discovery request, Kubernetes returns list of 3 IP addresses. JGroups now knows that the ports have been
  allocated from range [`7800` .. `7801`] (`bind_port` .. (`bind_port` + `port_range`) in `TCP`).
  
  KUBE_PING therefore sends discovery requests to members at addresses `172.17.0.2:7800`, `172.17.0.2:7801`, `172.17.0.3:7800`,
  `172.17.0.3:7801`, `172.17.0.5:7800` and `172.17.0.5:7801`.
  
  
  == Separating different clusters
  