anchor.diff:  route.route.openshift.io/hello-openshift exposed
   ----
   +
  -.. Verify route domain change:
  +.Example output:
   +
   [source,terminal]
   ----
   $ oc get routes
   NAME              HOST/PORT                                   PATH   SERVICES          PORT       TERMINATION   WILDCARD
  -hello-openshift   hello-openshift-my-project.apps.acme.io          hello-openshift   8080-tcp                 None
  +hello-openshift   hello_openshift-<my_project>.test.example.com
  +hello-openshift   8080-tcp                 None
   ----
  
positive.code: metadata:
    name: cluster
  spec:
    domain: apps.<domain_url>
    appsDomain: apps.acme.io
  ----
  +
  . Verify that an existing route contains the new domain name by exposing the route and verifying the route domain change:
  //+
  //.. Access the Ingress Controller Operator YAML file:
  //+
  
negative.code: 
  //OpenShift Dedicated or Amazon RH OpenShift cluster administrator
  
  As a cluster administrator, you can specify an alternative to the default cluster domain for user-created routes by configuring the `appsDomain` field. The `appsDomain` field is an optional domain for AWS infrastructure to use instead of the default, which is specified in the `domain` field. If you specify an alternative domain, it overrides the default cluster domain for the purpose of determining the default host for a new route.
  
  For example, you can use the DNS domain for your company as the default domain for routes and ingresses for applications running on your cluster.
  
  