Merge pull request #77401 from JoeAldinger/ROSA-OSDOCS-10005

/lgtm OSDOCS-1005:removes limitation of InFW on ROSA and AWS

Author: JoeAldinger

_topic_maps/_topic_map_rosa.yml

@@ -1059,8 +1059,9 @@ Topics:
   File: configuring-cluster-wide-proxy
 - Name: CIDR range definitions
   File: cidr-range-definitions
-- Name:  Network security
+- Name: Network security
   Dir: network_security
+  Distros: openshift-rosa
   Topics:
   - Name: Understanding network policy APIs
     File: network-policy-apis
@@ -1090,6 +1091,8 @@ Topics:
       File: default-network-policy
     - Name: Configuring multitenant isolation with network policy
       File: multitenant-network-policy
+  - Name: Understanding the Ingress Node Firewall Operator
+    File: ingress-node-firewall-operator
 - Name: OVN-Kubernetes network plugin
   Dir: ovn_kubernetes_network_provider
   Topics:

modules/nw-infw-operator-cr.adoc

@@ -17,6 +17,4 @@ The Ingress Node Firewall Operator supports only stateless firewall rules.
 Network interface controllers (NICs) that do not support native XDP drivers will run at a lower performance.
 
 For {product-title} 4.14 or later, you must run Ingress Node Firewall Operator on {op-system-base} 9.0 or later.
-
-Ingress Node Firewall Operator is not supported on {aws-first} with the default OpenShift installation or on {product-rosa} (ROSA). For more information on {product-rosa} support and ingress, see link:https://docs.openshift.com/rosa/networking/ingress-operator.html[Ingress Operator in Red Hat OpenShift Service on AWS].
 ====