[enterprise-4.2] PR16963 Follow-up

modules/nw-ingress-default-internal.adoc

@@ -0,0 +1,43 @@
+// Module included in the following assemblies:
+//
+// * networking/ingress-operator.adoc
+
+[id="nw-ingress-default-internal_{context}"]
+= Configuring the default Ingress Controller for your cluster to be internal
+
+You can configure the `default` Ingress Controller for your cluster to be internal by deleting and recreating it.
+
+[WARNING]
+====
+If your cloud provider is Microsoft Azure, you must have at least one public load balancer that points to your nodes.
+If you do not, all of your nodes will lose egress connectivity to the internet.
+====
+
+[IMPORTANT]
+====
+If you want to change the `scope` for an `IngressController` object, you must delete and then recreate that `IngressController` object. You cannot change the `.spec.endpointPublishingStrategy.loadBalancer.scope` parameter after the Custom Resource (CR) is created.
+====
+
+.Prerequisites
+
+* Install the OpenShift command-line interface (CLI), commonly known as `oc`.
+* Log in as a user with `cluster-admin` privileges.
+
+.Procedure
+
+. Configure the `default` Ingress Controller for your cluster to be internal by deleting and recreating it.
++
+----
+$ oc replace --force --wait --filename - <<EOF
+apiVersion: operator.openshift.io/v1
+kind: IngressController
+metadata:
+  namespace: openshift-ingress-operator
+  name: default
+spec:
+  endpointPublishingStrategy:
+    type: LoadBalancerService
+    loadBalancer:
+      scope: Internal
+EOF
+----

modules/nw-ingress-setting-internal-lb.adoc

@@ -8,12 +8,10 @@
 When creating an Ingress Controller on cloud platforms, the Ingress Controller is published by a public cloud load balancer by default.
 As an administrator, you can create an Ingress Controller that uses an internal cloud load balancer.
 
-You can configure the `default` Ingress Controller for your cluster to be internal by deleting and recreating it.
-
 [WARNING]
 ====
-If your cloud provider is Azure, you must have at least one public load balancer that points to your nodes.
-If you do not, all of your nodes will lose egress connectivity to the Internet.
+If your cloud provider is Microsoft Azure, you must have at least one public load balancer that points to your nodes.
+If you do not, all of your nodes will lose egress connectivity to the internet.
 ====
 
 [IMPORTANT]
@@ -26,7 +24,7 @@ for implementation details.
 
 .Prerequisites
 
-* Install the OpenShift Command-line Interface (CLI), commonly known as `oc`.
+* Install the OpenShift command-line interface (CLI), commonly known as `oc`.
 * Log in as a user with `cluster-admin` privileges.
 
 .Procedure
@@ -49,7 +47,6 @@ spec:
 ----
 <1> Replace `<name>` with a name for the `IngressController` object.
 <2> Specify the `domain` for the application published by the controller.
-If the `name` for the controller is `default` and you do not specify the `domain` parameter, the default cluster domain is used.
 <3> Specify a value of `Internal` to use an internal load balancer.
 
 . Create the Ingress Controller defined in the previous step by running the following command:

networking/ingress-operator.adoc

@@ -37,6 +37,8 @@ include::modules/nw-ingress-sharding-namespace-labels.adoc[leveloffset=+1]
 
 include::modules/nw-ingress-setting-internal-lb.adoc[leveloffset=+1]
 
+include::modules/nw-ingress-default-internal.adoc[leveloffset=+1]
+
 //include::modules/nw-ingress-select-route.adoc[leveloffset=+1]
 
 == Additional resources