anchor.diff:  If you are on an machine outside the cluster and are trying to access
   a resource provided by the cluster there needs to be a process running
   in a pod that listens on a public IP address and "routes" that traffic
  -inside the cluster.  The link:[OpenShift router] serves that purpose
  -for HTTP, HTTPS (with SNI), WebSockets, or TLS (with SNI).
  +inside the cluster.  The
  +link:../architecture/core_concepts/routes.html[OpenShift router]
  +serves that purpose for HTTP, HTTPS (with SNI), WebSockets, or TLS
  +(with SNI).
   
   Assuming you can't access an HTTP service from the outside of the
   cluster, let's start by reproducing the problem on the command line of
  
positive.code: 
  Now that you have an IP address, we need to `ssh` to that machine and
  check that the router software is running on that machine and
  configured correctly.  So let's `ssh` there and make sure the router
  is running:
  ....
  # oc get endpoints --namespace=default --label=router
  NAMESPACE   NAME              ENDPOINTS
  
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.
  