anchor.diff:  == Overview
   
   As described in the
  -link:/architecture/additional_concepts/sdn.html[SDN documentation]
  +link:../architecture/additional_concepts/sdn.html[SDN documentation]
   there are multiple layers of interfaces that are created to correctly
   pass the traffic from one container to another.  In order to debug
   connectivity issues, you have to test the different layers of the
  
positive.code: backs that service.  So you should be able to talk to that IP address.
  But, unfortunately, even if you can, it doesn't mean all pods are reachable;
  and if you can't, it doesn't mean all pods aren't reachable.  It just
  tells you the status of the /one/ that kubproxy hooked you up to.
  
  Let's test the service anyway.  From one of your nodes:
  ....
  
negative.code: 
  == Nomenclature
  
  Cluster:: The set of machines in the cluster.  _i.e._ the Masters
  and the Nodes.
  Master:: A controller of the OpenShift cluster.  Note that the
  master may not be a node in the cluster, and thus, may not have IP
  connectivity to the pods.
  Node:: Host in the cluster running OpenShift that can host pods.
  Pod:: Group of containers running on a node, managed by OpenShift.
  Service:: Abstraction that presents a unified network interface that
  is backed by one or more pods.
  