anchor.diff:  $ oc project otherns
   $ oc expose service thirdservice --hostname=emmy.example.test
   $ oc expose service thirdservice --hostname=webby.example.test
  -
  -----
  -
  -
  -In the example below, a router that allows wildcard routes will not allow
  -the claim for `owner.example.test` or `aname.example.test` to succeed
  -since the owning namespace is `ns1`.
  +----
  +
  +In the example below, a router that allows wildcard routes will not allow the
  +claim for `owner.example.test` or `aname.example.test` to succeed since the
  +owning namespace is `ns1`.
   
   ----
   $ oadm router ...
  
positive.code: $ oc create -f route.yaml   #  router will allow this claim.
  ----
  
  
  In the example below, a router that allows wildcard routes will not allow
  the claim for \*.example.test to succeed since the owning namespace is `ns1`
  and the wildcard route belongs to another namespace `cyclone`.
  
  ----
  
negative.code: 
  $ # namespace `otherns` is not allowed to claim for unclaimed.example.test
  $ oc expose service yetanotherservice --hostname=unclaimed.example.test
  ----
  
  In the example below,  different scenarios are shown, in which the owner routes
  are deleted and ownership is passed within and across namespaces. While a route
  claiming host `eldest.example.test` in the namespace `ns1` exists, wildcard
  routes in that namespace can claim subdomain `example.test`. When the route for
  host `eldest.example.test` is deleted, the next oldest route
  `senior.example.test` would become the oldest route and would not affect any
  other routes. Once the route for host `senior.example.test` is deleted, the next
  oldest route `junior.example.test` becomes the oldest route and block the
  wildcard route claimant.
  
  ----
  