Added allow-from-router part and given the same references in other respective sections.

Author: subhtk

modules/nw-networkpolicy-about.adoc

@@ -123,3 +123,49 @@ spec:
 `NetworkPolicy` objects are additive, which means you can combine multiple `NetworkPolicy` objects together to satisfy complex network requirements.
 
 For example, for the `NetworkPolicy` objects defined in previous samples, you can define both `allow-same-namespace` and `allow-http-and-https` policies within the same project. Thus allowing the pods with the label `role=frontend`, to accept any connection allowed by each policy. That is, connections on any port from pods in the same namespace, and connections on ports `80` and `443` from pods in any namespace.
+
+[id="nw-networkpolicy-allow-from-router_{context}"]
+== Using the allow-from-router network policy
+
+Use the following `NetworkPolicy` to allow external traffic regardless of the router configuration:
+
+[source,yaml]
+----
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: allow-from-router
+spec:
+  ingress:
+  - from:
+    - namespaceSelector:
+        matchLabels:
+          policy-group.network.openshift.io/ingress:""<1>
+  podSelector: {}
+  policyTypes:
+  - Ingress
+----
+<1> `policy-group.network.openshift.io/ingress:""` label supports both Openshift-SDN and OVN-Kubernetes.
+
+
+[id="nw-networkpolicy-allow-from-hostnetwork_{context}"]
+== Using the allow-from-hostnetwork network policy
+
+Add the following `allow-from-hostnetwork` `NetworkPolicy` object to direct traffic from the host network pods:
+
+[source,yaml]
+----
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: allow-from-hostnetwork
+spec:
+  ingress:
+  - from:
+    - namespaceSelector:
+        matchLabels:
+          policy-group.network.openshift.io/host-network:""
+  podSelector: {}
+  policyTypes:
+  - Ingress
+----

networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc

@@ -55,8 +55,12 @@ include::modules/nw-ingress-sharding-route-configuration.adoc[leveloffset=+1]
 [role="_additional-resources"]
 == Additional resources
 
-* The Ingress Operator manages wildcard DNS. For more information, see
-xref:../../networking/ingress-operator.adoc#configuring-ingress[Ingress Operator in {product-title}],
-xref:../../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Installing a cluster on bare metal], and
-xref:../../installing/installing_vsphere/installing-vsphere.adoc#installing-vsphere[Installing a cluster on vSphere].
-endif::[]
+The Ingress Operator manages wildcard DNS. For more information, see the following:
+
+* xref:../../networking/ingress-operator.adoc#configuring-ingress[Ingress Operator in {product-title}].
+
+* xref:../../installing/installing_bare_metal/installing-bare-metal.adoc#installing-bare-metal[Installing a cluster on bare metal].
+
+* xref:../../installing/installing_vsphere/installing-vsphere.adoc#installing-vsphere[Installing a cluster on vSphere].
+
+* xref:../../networking/network_policy/about-network-policy.adoc#about-network-policy[About network policy].