anchor.diff:  $ oc create -f route.yaml   #  router will deny (_NOT_ allow) this claim.
   ----
   
  -
  -In a similar vein, once a namespace with a wildcard route claims a
  -subdomain, only routes within that namespace can claim any hosts in that
  -same subdomain.
  +Similarly, once a namespace with a wildcard route claims a subdomain, only
  +routes within that namespace can claim any hosts in that same subdomain.
   
   In the example below, once a route in namespace `ns1` with a wildcard route
  -claims subdomain `example.test`, only routes in the namespace `ns1` will be
  -allowed to claim any hosts in that same subdomain.
  +claims subdomain `example.test`, only routes in the namespace `ns1` are allowed
  +to claim any hosts in that same subdomain.
   
   ----
   $ oadm router ...
  
positive.code: $ # `dos.example.test` would be unaffected as there are no other wildcard
  $ # claimants blocking it.
  $ oc delete route seniorservice
  
  ----
  
  
  [[using-the-container-network-stack]]
  == Using the Container Network Stack
  
negative.code: # curl -k --resolve anyname.example.test:443:$routerip https://anyname.example.test/
  ----
  
  For routers that allow wildcard routes (`ROUTER_ALLOW_WILDCARD_ROUTES` set to
  `true`), there are some caveats to the ownership of a subdomain associated with
  a wildcard route.
  
  Prior to wildcard routes, ownership was based on the claims made for a host name
  with the namespace with the oldest route winning against any other claimants.
  For example, route `r1` in namespace `ns1` with a claim for `one.example.test`
  would win over another route `r2` in namespace `ns2` for the same host name
  `one.example.test` if route `r1` was older than route `r2`.
  
  In addition, routes in other namespaces were allowed to claim non-overlapping
  hostnames. For example, route `rone` in namespace `ns1` could claim
  `www.example.test` and another route `rtwo` in namespace `d2` could claim
  `c3po.example.test`.
  
  This is still the case if there are _no_ wildcard routes claiming that same
  subdomain (`example.test` in the above example).
  
  However, a wildcard route needs to claim all of the host names within a
  subdomain (host names of the form `\*.example.test`). A wildcard route's claim
  is allowed or denied based on whether or not the oldest route for that subdomain
  (`example.test`) is in the same namespace as the wildcard route. The oldest
  route can be either a regular route or a wildcard route.
  
  For example, if there is already a route `eldest` that exists in the `ns1`
  namespace that claimed a host named `owner.example.test` and, if at a later
  point in time, a new wildcard route `wildthing` requesting for routes in that
  subdomain (`example.test`) is added, the claim by the wildcard route will _only_
  be allowed if it is the same namespace (`ns1`) as the owning route.
  
  The following examples illustrate various scenarios in which claims for wildcard
  routes will succeed or fail.
  
  In the example below, a router that allows wildcard routes will allow
  non-overlapping claims for hosts in the subdomain `example.test` as long as a
  wildcard route has not claimed a subdomain.
  
  ----
  $ oadm router ...
  