OSDOCS#8394: Migrated the Networking topic for the Deploying your App…

…lication docs

_topic_maps/_topic_map_rosa.yml

@@ -156,6 +156,8 @@ Topics:
       File: cloud-experts-getting-started-simple-ui-guide
     - Name: Detailed UI guide
       File: cloud-experts-getting-started-detailed-ui
+    - Name: Networking
+      File: cloud-experts-deploying-application-networking
   - Name: Creating an admin user
     File: cloud-experts-getting-started-admin
   - Name: Setting up an identity provider

cloud_experts_tutorials/cloud-experts-deploying-application/cloud-experts-deploying-application-networking.adoc

@@ -0,0 +1,52 @@
+:_mod-docs-content-type: ASSEMBLY
+[id="cloud-experts-deploying-application-intro"]
+= Tutorial: Networking
+include::_attributes/attributes-openshift-dedicated.adoc[]
+:context: cloud-experts-deploying-application-networking
+
+toc::[]
+
+//rosaworkshop.io content metadata
+//Brought into ROSA product docs 2023-12-14
+
+This tutorial shows how the OSToy app uses intra-cluster networking to separate functions by using microservices and visualize the scaling of pods.
+
+image::deploying-networking-arch.png[OSToy Diagram]
+
+The image shows there are at least 2 separate pods, each with its own service. One pod functions as the frontend web application with a service and a publicly accessible route. The other pod functions as the backend microservice with a service object so that the frontend pod can communicate with the microservice. This communication occurs across the pods if more than one. Therefore this microservice is not accessible from outside this cluster, or from other namespaces/projects if configured (due to OpenShift's network policy, xref:../../networking/openshift_network_security/network_policy/about-network-policy.adoc#about-network-policy[About network policy]. The sole purpose of this microservice is to serve internal web requests and return a JSON object containing the current hostname (which is the pod name) and a randomly generated color string. This color string is used to display a box with that color displayed in the tile titled "Intra-cluster Communication".
+
+== Networking types
+
+. Intra-cluster networking
++
+Click on *Networking* in the left menu. Review the networking configuration. The right tile titled "Hostname Lookup" illustrates how the service name created for a pod can be used to translate into an internal ClusterIP address.
+
+. Lookup internal IP address of the service
++
+Enter the name of the microservice we created in the right tile ("Hostname Lookup") following the format of `my-svc.my-namespace.svc.cluster.local` which we created in the service definition of `ostoy-microservice.yaml` which can be seen here:
++
+[source,yaml]
+====
+apiVersion: v1
+kind: Service
+metadata:
+  name: ostoy-microservice-svc
+  labels:
+    app: ostoy-microservice
+spec:
+  type: ClusterIP
+  ports:
+    - port: 8080
+      targetPort: 8080
+      protocol: TCP
+  selector:
+    app: ostoy-microservice
+====
++
+In this case we will enter: `ostoy-microservice-svc.ostoy.svc.cluster.local`
+
+. IP address returned
++
+We will see an IP address returned. In our example it is `172.30.165.246`. This is the intra-cluster IP address; only accessible from within the cluster.
++
+image::deploying-networking-dns.png[OSToy DNS]