KUBERNETES_USE_NOT_READY_ADDRESSES functionality

fixes #77

Author: slaskawi

README.adoc

@@ -171,6 +171,8 @@ namespace `"default"` will be returned.
 
 | split_clusters_during_rolling_update | KUBERNETES_SPLIT_CLUSTERS_DURING_ROLLING_UPDATE | During the Rolling Update, prevents from putting all Pods into a single cluster
 
+| useNotReadyAddresses | KUBERNETES_USE_NOT_READY_ADDRESSES | True if initial discovery should take unready Pods into consideration. Default is `true`.
+
 |===============
 
 

src/main/java/org/jgroups/protocols/kubernetes/KUBE_PING.java

@@ -105,9 +105,12 @@ public class KUBE_PING extends Discovery {
 
     @Property(description="The standard behavior during Rolling Update is to put all Pods in the same cluster. In" +
           " cases (application level incompatibility) this causes problems. One might decide to split clusters to" +
-          " 'old' and 'new' during that process", systemProperty="SPLIT_CLUSTERS_DURING_ROLLING_UPDATE")
+          " 'old' and 'new' during that process", systemProperty="KUBERNETES_SPLIT_CLUSTERS_DURING_ROLLING_UPDATE")
     protected boolean split_clusters_during_rolling_update;
 
+    @Property(description="Introduces similar behaviour to Kubernetes Services (using DNS) with publishNotReadyAddresses set to true." +
+            "By default it's true", systemProperty="KUBERNETES_USE_NOT_READY_ADDRESSES")
+    protected boolean useNotReadyAddresses = true;
 
     protected Client  client;
 
@@ -217,7 +220,7 @@ public void findMembers(List<Address> members, boolean initial_discovery, Respon
             if(log.isTraceEnabled())
                 log.trace("%s: hosts fetched from Kubernetes: %s", local_addr, hosts);
             for(Pod host: hosts) {
-                if (!host.isReady())
+                if (!host.isReady() && !useNotReadyAddresses)
                     continue;
                 for(int i=0; i <= port_range; i++) {
                     try {