anchor.diff:  ----
   ====
   
  -.An Unsecure Route with a Path:
  +.An Unsecured Route with a Path:
   ====
   
   ----
  
positive.code: test routes, an install command is provided.
  
  
  Check the default router ("router"):
  
  ****
  $ `oadm router --dry-run`
  ****
  
  See what the router would look like if created:
  
  ****
  $ `oadm router -o json`
  ****
  
  Create a router if it does not exist:
  
  ****
  $ `oadm router router-west --replicas=2 --credentials="$KUBECONFIG"`
  ****
  
  Use a different router image and see the router configuration:
  
  ****
  $ `oadm router region-west -o yaml --images=myrepo/somerouter:mytag`
  ****
  
  NOTE: This command is currently being actively developed. It is intended to simplify the tasks of setting up routers in a new installation.
  
  The following diagram illustrates how data flows from the master through the
  plug-in and finally into an HAProxy configuration:
  
negative.code: - WebSockets
  - TLS with SNI
  
  [NOTE]
  WebSocket traffic uses the same route conventions and supports the same
  TLS termination types as other traffic.
  
  The router uses the service selector to watch the endpoints that support the
  service, bypassing its logic and replacing it with the router's own. Routers
  subscribe to a configuration and automatically update themselves when the
  configuration changes. A router may be containerized or virtual, converting any
  changes to API calls to another system, such as *F5*.
  
  Other capabilities exist to load-balance a service within a cluster. These
  services are exposed via a configurable link relation between different
  