OCPBUGS#9407: Update the ingress controller sharding procedure

Author: xenolinux

modules/nw-ingress-sharding-namespace-labels.adoc

@@ -39,7 +39,7 @@ items:
     name: sharded
     namespace: openshift-ingress-operator
   spec:
-    domain: <apps-sharded.basedomain.example.net>
+    domain: <apps-sharded.basedomain.example.net> <1>
     nodePlacement:
       nodeSelector:
         matchLabels:
@@ -53,6 +53,7 @@ metadata:
   resourceVersion: ""
   selfLink: ""
 ----
+<1> Specify a domain to be used by the Ingress Controller. This domain must be different from the default Ingress Controller domain.
 
 . Apply the Ingress Controller `router-internal.yaml` file:
 +
@@ -63,3 +64,10 @@ metadata:
 +
 The Ingress Controller selects routes in any namespace that is selected by the
 namespace selector that have the label `type: sharded`.
+
+. Create a new route using the domain configured in the `router-internal.yaml`:
++
+[source,terminal]
+----
+$ oc expose svc <service-name> --hostname <route-name>.apps-sharded.basedomain.example.net
+----

modules/nw-ingress-sharding-route-labels.adoc

@@ -34,7 +34,7 @@ items:
     name: sharded
     namespace: openshift-ingress-operator
   spec:
-    domain: <apps-sharded.basedomain.example.net>
+    domain: <apps-sharded.basedomain.example.net> <1>
     nodePlacement:
       nodeSelector:
         matchLabels:
@@ -48,6 +48,7 @@ metadata:
   resourceVersion: ""
   selfLink: ""
 ----
+<1> Specify a domain to be used by the Ingress Controller. This domain must be different from the default Ingress Controller domain.
 
 . Apply the Ingress Controller `router-internal.yaml` file:
 +
@@ -58,3 +59,10 @@ metadata:
 +
 The Ingress Controller selects routes in any namespace that have the label
 `type: sharded`.
+
+. Create a new route using the domain configured in the `router-internal.yaml`:
++
+[source,terminal]
+----
+$ oc expose svc <service-name> --hostname <route-name>.apps-sharded.basedomain.example.net
+----