anchor.diff:  We can now run a shell in one of the nodes and confirm that a cluster of 3 has formed. First, we have to exec a bash shell
   in one of the 3 nodes:
   ----
  -ispn-perf-test-2224433472-rlr0m   1/1       Running   0          5m
   [belasmac] /Users/bela/kubetest$ kubectl exec -it ispn-perf-test-2224433472-rlr0m bash
   bash-4.3$
   ----
  
positive.code: cluster=default
  version=4.0.3-SNAPSHOT (Schiener Berg)
  
  
  
  3 responses (3 matches, 0 non matches)
  bash-4.3$
  ----
  
  As can be seen, every member has the same view `ispn-perf-test-2224433472-ksh58-1200|2] (3)` containing 3 members, so
  
negative.code: Similarly to namespaces, labels also have to be defined when launching a pod, either via `--labels=<label>` passed
  to `kubectl run`, or in the YAML or JSON configuration file passed to `kubectl create -f <config>`.
  
  In the sample configuration above, labels were defined as `labels="${KUBE_LABEL:cluster=nyc}"`. This means that
  Kubernetes will only return IP addresses of pods started with label `cluster=nyc`.
  
  Namespaces and labels can be both set; in this case, Kubernetes will return the IP addresses of all pods started in
  