OSDOCS-3205: Added information about the Network Ingress to OCM book

.vscode/settings.json

@@ -0,0 +1,22 @@
+{
+    "workbench.colorCustomizations": {
+        "activityBar.activeBackground": "#1f6fd0",
+        "activityBar.activeBorder": "#ee90bb",
+        "activityBar.background": "#1f6fd0",
+        "activityBar.foreground": "#e7e7e7",
+        "activityBar.inactiveForeground": "#e7e7e799",
+        "activityBarBadge.background": "#ee90bb",
+        "activityBarBadge.foreground": "#15202b",
+        "sash.hoverBorder": "#1f6fd0",
+        "statusBar.background": "#1857a4",
+        "statusBar.foreground": "#e7e7e7",
+        "statusBarItem.hoverBackground": "#1f6fd0",
+        "statusBarItem.remoteBackground": "#1857a4",
+        "statusBarItem.remoteForeground": "#e7e7e7",
+        "titleBar.activeBackground": "#1857a4",
+        "titleBar.activeForeground": "#e7e7e7",
+        "titleBar.inactiveBackground": "#1857a499",
+        "titleBar.inactiveForeground": "#e7e7e799"
+    },
+    "peacock.color": "#1857a4"
+}

architecture/ocm-overview-ocp.adoc

@@ -46,7 +46,6 @@ Selecting an active, installed cluster shows tabs associated with that cluster.
 include::modules/ocm-overview-tab.adoc[leveloffset=+2]
 include::modules/ocm-accesscontrol-tab.adoc[leveloffset=+2]
 include::modules/ocm-addons-tab.adoc[leveloffset=+2]
-include::modules/ocm-networking-tab.adoc[leveloffset=+2]
 include::modules/ocm-insightsadvisor-tab.adoc[leveloffset=+2]
 include::modules/ocm-machinepools-tab.adoc[leveloffset=+2]
 include::modules/ocm-support-tab.adoc[leveloffset=+2]

modules/ocm-networking-tab-adding-ingress.adoc

@@ -0,0 +1,22 @@
+// Module included in the following assemblies:
+//
+// ocm/ocm-overview.adoc
+:_content-type: PROCEDURE
+[id="ocm-networking-tab-adding-ingress_{context}"]
+= Adding a network Ingress to your {product-title} cluster
+
+You can add a network Ingress to your cluster from the {cluster-manager-url} web UI.
+
+.Prerequisites
+
+* You have a Red Hat account.
+* You have the required permissions to make changes to your cluster in {cluster-manager}.
+
+.Procedure
+
+. From the **Networking** tab in {cluster-manager}, click the **Additional application router** toggle to enable the Ingress. There are two options you can add to the additional router:
+.. **Make router private**: This checkbox allows you to control cluster privacy. By default, your Ingress router is publicly exposed and allows anyone access. You can limit access to applications or websites you run on your cluster by selecting this checkbox. For example, if you only want internal employees to access this cluster, then using this option requires a private connection, such as a virtual private network (VPN) or virtual private cloud (VPC) peering connection. 
+.. **Label match for additional router**: This field provides a way to target the specific route you want exposed in this additional Ingress router. By default, the router exposes all routes. If you leave this field blank, these routes stay exposed. 
++
+A commonly used setup has a private default router, which means any applications deployed require a VPN or VPC peering to access. You can create an additional public router with a label match of  `route=external`. Then, if you add the `route=external` label to additional routes, the additional router matches this label and exposes it for public use.
+. Click **Change settings** to confirm that you want to add the network Ingress.

modules/ocm-networking-tab-concept.adoc

@@ -1,20 +1,22 @@
 // Module included in the following assemblies:
 //
 // ocm/ocm-overview.adoc
-
+:_content-type: CONCEPT
 [id="ocm-networking-tab_{context}"]
 = Networking tab
 
 The **Networking** tab provides a control plane API endpoint as well as the default application router. Both the control plane API endpoint and the default application router can be made private by selecting the respective box below each of them.
 
-[NOTE]
+ifdef::openshift-rosa[]
+[IMPORTANT]
 ====
-For Security Token Service (STS) installations, these options cannot be changed.
+For Security Token Service (STS) installations, these options cannot be changed. STS installations also do not allow you to change privacy nor allow you to add an additional router.
 ====
+endif::openshift-rosa[]
 
 ifndef::openshift-rosa[]
 [IMPORTANT]
 ====
-{cluster-manager-first} does not support the networking tab for {GCP} clusters unless the organization has the `capability.organization.create_gcp_non_ccs_cluster` permission attached.
+{cluster-manager-first} does not support the networking tab for a Google Cloud Platform (GCP), non-CCS cluster running in a Red Hat GCP project.
 ====
 endif::openshift-rosa[]

ocm/ocm-overview.adoc

@@ -46,7 +46,10 @@ Selecting an active, installed cluster shows tabs associated with that cluster.
 include::modules/ocm-overview-tab.adoc[leveloffset=+2]
 include::modules/ocm-accesscontrol-tab.adoc[leveloffset=+2]
 include::modules/ocm-addons-tab.adoc[leveloffset=+2]
-include::modules/ocm-networking-tab.adoc[leveloffset=+2]
+include::modules/ocm-networking-tab-concept.adoc[leveloffset=+2]
+ifndef::openshift-rosa[]
+include::modules/ocm-networking-tab-adding-ingress.adoc[leveloffset=+3]
+endif::openshift-rosa[]
 include::modules/ocm-insightsadvisor-tab.adoc[leveloffset=+2]
 include::modules/ocm-machinepools-tab.adoc[leveloffset=+2]
 include::modules/ocm-support-tab.adoc[leveloffset=+2]