networking overview

Ingress and load balancing

Advanced networking

configuring network settings

_attributes/_attributes

@@ -1 +1 @@
-../../../_attributes/
+../../_attributes/

_topic_maps/_topic_map.yml

@@ -1386,12 +1386,18 @@ Name: Networking
 Dir: networking
 Distros: openshift-enterprise,openshift-origin
 Topics:
-- Name: Understanding networking
-  File: understanding-networking
-- Name: Accessing hosts
-  File: accessing-hosts
-- Name: Networking dashboards
-  File: networking-dashboards
+- Name: Networking overview
+  Dir: networking_overview
+  Distros: openshift-enterprise,openshift-origin
+  Topics:
+  - Name: Understanding networking
+    File: understanding-networking
+  - Name: Accessing hosts
+    File: accessing-hosts
+  - Name: Networking dashboards
+    File: networking-dashboards
+  - Name: CIDR range definitions
+    File: cidr-range-definitions
 - Name: Networking Operators
   Dir: networking_operators
   Distros: openshift-enterprise,openshift-origin
@@ -1546,37 +1552,6 @@ Topics:
     File: configuring-ipsec-ovn
   - Name: Zero trust networking
     File: zero-trust-networking
-- Name: Configuring the Ingress Controller for manual DNS management
-  File: ingress-controller-dnsmgt
-  Distros: openshift-enterprise,openshift-origin
-- Name: Verifying connectivity to an endpoint
-  File: verifying-connectivity-endpoint
-- Name: Changing the cluster network MTU
-  File: changing-cluster-network-mtu
-- Name: Configuring the node port service range
-  File: configuring-node-port-service-range
-- Name: Configuring the cluster network IP address range
-  File: configuring-cluster-network-range
-- Name: Configuring IP failover
-  File: configuring-ipfailover
-- Name: Configuring system controls and interface attributes using the tuning plugin
-  File: configure-syscontrols-interface-tuning-cni
-- Name: Using Stream Control Transmission Protocol
-  File: using-sctp
-  Distros: openshift-enterprise,openshift-origin
-- Name: Using PTP hardware
-  Dir: ptp
-  Topics:
-  - Name: About PTP in OpenShift cluster nodes
-    File: about-ptp
-  - Name: Configuring PTP devices
-    File: configuring-ptp
-  - Name: Developing PTP events consumer applications with the REST API v2
-    File: ptp-cloud-events-consumer-dev-reference-v2
-  - Name: PTP events REST API v2 reference
-    File: ptp-events-rest-api-reference-v2
-- Name: CIDR range definitions
-  File: cidr-range-definitions
 - Name: Multiple networks
   Dir: multiple_networks
   Distros: openshift-enterprise,openshift-origin
@@ -1682,52 +1657,112 @@ Topics:
     File: tracking-network-flows
   - Name: Configuring hybrid networking
     File: configuring-hybrid-networking
-- Name: Configuring Routes
-  Dir: routes
+- Name: Ingress and load balancing
+  Dir: ingress_load_balancing
+  Distros: openshift-enterprise,openshift-origin
   Topics:
-  - Name: Route configuration
-    File: route-configuration
-  - Name: Secured routes
-    File: secured-routes
-- Name: Configuring ingress cluster traffic
-  Dir: configuring_ingress_cluster_traffic
+  - Name: Configuring Routes
+    Dir: routes
+    Distros: openshift-enterprise,openshift-origin
+    Topics:
+    - Name: Route configuration
+      File: route-configuration
+    - Name: Secured routes
+      File: secured-routes
+  - Name: Configuring ingress cluster traffic
+    Dir: configuring_ingress_cluster_traffic
+    Distros: openshift-enterprise,openshift-origin
+    Topics:
+    - Name: Overview
+      File: overview-traffic
+    - Name: Configuring ExternalIPs for services
+      File: configuring-externalip
+    - Name: Configuring ingress cluster traffic using an Ingress Controller
+      File: configuring-ingress-cluster-traffic-ingress-controller
+    - Name: Configuring the Ingress Controller endpoint publishing strategy
+      File: nw-configuring-ingress-controller-endpoint-publishing-strategy
+    - Name: Configuring ingress cluster traffic using a load balancer
+      File: configuring-ingress-cluster-traffic-load-balancer
+    - Name: Configuring ingress cluster traffic on AWS
+      File: configuring-ingress-cluster-traffic-aws
+    - Name: Configuring ingress cluster traffic using a service external IP
+      File: configuring-ingress-cluster-traffic-service-external-ip
+    - Name: Configuring ingress cluster traffic using a NodePort
+      File: configuring-ingress-cluster-traffic-nodeport
+    - Name: Configuring ingress cluster traffic using load balancer allowed source ranges
+      File: configuring-ingress-cluster-traffic-load-balancer-allowed-source-ranges
+    - Name: Patching existing ingress objects
+      File: configuring-ingress-cluster-patch-fields
+    - Name: Allocating load balancers to specific subnets
+      File: allocating-load-balancers
+    - Name: Configuring the Ingress Controller for manual DNS management
+      File: ingress-controller-dnsmgt
+    - Name: Gateway API with OpenShift Container Platform networking
+      File: ingress-gateway-api
+  - Name: Load balancing on OpenStack
+    File: load-balancing-openstack
+  - Name: Load balancing with MetalLB
+    Dir: metallb
+    Distros: openshift-enterprise,openshift-origin
+    Topics:
+    - Name: Configuring MetalLB address pools
+      File: metallb-configure-address-pools
+    - Name: Advertising the IP address pools
+      File: about-advertising-ipaddresspool
+    - Name: Configuring MetalLB BGP peers
+      File: metallb-configure-bgp-peers
+    - Name: Advertising an IP address pool using the community alias
+      File: metallb-configure-community-alias
+    - Name: Configuring MetalLB BFD profiles
+      File: metallb-configure-bfd-profiles
+    - Name: Configuring services to use MetalLB
+      File: metallb-configure-services
+    - Name: Managing symmetric routing with MetalLB
+      File: metallb-configure-return-traffic
+    - Name: Configuring the integration of MetalLB and FRR-K8s
+      File: metallb-frr-k8s
+    - Name: MetalLB logging, troubleshooting, and support
+      File: metallb-troubleshoot-support
+- Name: Configuring network settings
+  Dir: configuring_network_settings
+  Distros: openshift-enterprise,openshift-origin
   Topics:
-  - Name: Overview
-    File: overview-traffic
+  - Name: Configuring system controls and interface attributes using the tuning plugin
+    File: configure-syscontrols-interface-tuning-cni
+  - Name: Configuring the node port service range
+    File: configuring-node-port-service-range
+  - Name: Configuring the cluster network IP address range
+    File: configuring-cluster-network-range
+  - Name: Configuring IP failover
+    File: configuring-ipfailover
+  - Name: Configuring the cluster-wide proxy
+    File: enable-cluster-wide-proxy
+  - Name: Configuring a custom PKI
+    File: configuring-a-custom-pki
+- Name: Advanced networking
+  Dir: advanced_networking
+  Distros: openshift-enterprise, openshift-origin
+  Topics:
+  - Name: Verifying connectivity to an endpoint
+    File: verifying-connectivity-endpoint
+  - Name: Changing the cluster network MTU
+    File: changing-cluster-network-mtu
+  - Name: Using Stream Control Transmission Protocol
+    File: using-sctp
+  - Name: Associating secondary interfaces metrics to network attachments
+    File: associating-secondary-interfaces-metrics-to-network-attachments
+  - Name: Using PTP hardware
+    Dir: ptp
     Distros: openshift-enterprise,openshift-origin
-  - Name: Configuring ExternalIPs for services
-    File: configuring-externalip
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Configuring ingress cluster traffic using an Ingress Controller
-    File: configuring-ingress-cluster-traffic-ingress-controller
-  - Name: Configuring the Ingress Controller endpoint publishing strategy
-    File: nw-configuring-ingress-controller-endpoint-publishing-strategy
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Configuring ingress cluster traffic using a load balancer
-    File: configuring-ingress-cluster-traffic-load-balancer
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Configuring ingress cluster traffic on AWS
-    File: configuring-ingress-cluster-traffic-aws
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Configuring ingress cluster traffic using a service external IP
-    File: configuring-ingress-cluster-traffic-service-external-ip
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Configuring ingress cluster traffic using a NodePort
-    File: configuring-ingress-cluster-traffic-nodeport
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Configuring ingress cluster traffic using load balancer allowed source ranges
-    File: configuring-ingress-cluster-traffic-load-balancer-allowed-source-ranges
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Patching existing ingress objects
-    File: configuring-ingress-cluster-patch-fields
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Allocating load balancers to specific subnets
-    File: allocating-load-balancers
-    Distros: openshift-enterprise,openshift-origin
-  - Name: Gateway API with OpenShift Container Platform networking
-    File: ingress-gateway-api
-    Distros: openshift-enterprise
-  # Kubernetes NMState (TECHNOLOGY PREVIEW)
+    Topics:
+    - Name: About PTP in OpenShift cluster nodes
+      File: about-ptp
+    - Name: Configuring PTP devices
+      File: configuring-ptp
+    - Name: Developing PTP events consumer applications with the REST API v2
+      File: ptp-cloud-events-consumer-dev-reference-v2
+    - Name: PTP events REST API v2 reference
+      File: ptp-events-rest-api-reference-v2
 - Name: Kubernetes NMState
   Dir: k8s_nmstate
   Topics:
@@ -1735,37 +1770,6 @@ Topics:
     File: k8s-nmstate-updating-node-network-config
   - Name: Troubleshooting node network configuration
     File: k8s-nmstate-troubleshooting-node-network
-- Name: Configuring the cluster-wide proxy
-  File: enable-cluster-wide-proxy
-  Distros: openshift-enterprise,openshift-origin
-- Name: Configuring a custom PKI
-  File: configuring-a-custom-pki
-  Distros: openshift-enterprise,openshift-origin
-- Name: Load balancing on OpenStack
-  File: load-balancing-openstack
-- Name: Load balancing with MetalLB
-  Dir: metallb
-  Topics:
-  - Name: Configuring MetalLB address pools
-    File: metallb-configure-address-pools
-  - Name: Advertising the IP address pools
-    File: about-advertising-ipaddresspool
-  - Name: Configuring MetalLB BGP peers
-    File: metallb-configure-bgp-peers
-  - Name: Advertising an IP address pool using the community alias
-    File: metallb-configure-community-alias
-  - Name: Configuring MetalLB BFD profiles
-    File: metallb-configure-bfd-profiles
-  - Name: Configuring services to use MetalLB
-    File: metallb-configure-services
-  - Name: Managing symmetric routing with MetalLB
-    File: metallb-configure-return-traffic
-  - Name: Configuring the integration of MetalLB and FRR-K8s
-    File: metallb-frr-k8s
-  - Name: MetalLB logging, troubleshooting, and support
-    File: metallb-troubleshoot-support
-- Name: Associating secondary interfaces metrics to network attachments
-  File: associating-secondary-interfaces-metrics-to-network-attachments
 ---
 Name: Storage
 Dir: storage

_topic_maps/_topic_map_osd.yml

@@ -734,8 +734,13 @@ Name: Networking
 Dir: networking
 Distros: openshift-dedicated
 Topics:
-- Name: About networking
-  File: about-managed-networking
+- Name: Networking overview
+  Dir: networking_overview
+  Topics:
+  - Name: About networking
+    File: about-managed-networking
+  - Name: CIDR range definitions
+    File: cidr-range-definitions
 - Name: Networking Operators
   Dir: networking_operators
   Distros: openshift-dedicated
@@ -748,8 +753,6 @@ Topics:
   File: network-verification
 - Name: Configuring a cluster-wide proxy during installation
   File: configuring-cluster-wide-proxy
-- Name: CIDR range definitions
-  File: cidr-range-definitions
 - Name: Network security
   Dir: network_security
   Distros: openshift-dedicated
@@ -784,13 +787,17 @@ Topics:
   Topics:
   - Name: Enabling multicast for a project
     File: enabling-multicast
-- Name: Configuring Routes
-  Dir: routes
+- Name: Ingress and load balancing
+  Dir: ingress_load_balancing
+  Distros: openshift-dedicated
   Topics:
-  - Name: Route configuration
-    File: route-configuration
-  - Name: Secured routes
-    File: secured-routes
+    - Name: Configuring Routes
+      Dir: routes
+      Topics:
+      - Name: Route configuration
+        File: route-configuration
+      - Name: Secured routes
+        File: secured-routes
 ---
 Name: Building applications
 Dir: applications

_topic_maps/_topic_map_rosa.yml

@@ -982,8 +982,14 @@ Name: Networking
 Dir: networking
 Distros: openshift-rosa
 Topics:
-- Name: About networking
-  File: about-managed-networking
+- Name: Networking overview
+  Dir: networking_overview
+  Distros: openshift-rosa
+  Topics:
+  - Name: About networking
+    File: about-managed-networking
+  - Name: CIDR range definitions
+    File: cidr-range-definitions
 - Name: Networking Operators
   Dir: networking_operators
   Distros: openshift-rosa
@@ -1000,8 +1006,6 @@ Topics:
   File: network-verification
 - Name: Configuring a cluster-wide proxy during installation
   File: configuring-cluster-wide-proxy
-- Name: CIDR range definitions
-  File: cidr-range-definitions
 - Name: Network security
   Dir: network_security
   Distros: openshift-rosa
@@ -1050,13 +1054,18 @@ Topics:
   Topics:
   - Name: Enabling multicast for a project
     File: enabling-multicast
-- Name: Configuring Routes
-  Dir: routes
+- Name: Ingress and load balancing
+  Dir: ingress_load_balancing
+  Distros: openshift-rosa
   Topics:
-  - Name: Route configuration
-    File: route-configuration
-  - Name: Secured routes
-    File: secured-routes
+  - Name: Configuring Routes
+    Dir: routes
+    Distros: openshift-rosa
+    Topics:
+    - Name: Route configuration
+      File: route-configuration
+    - Name: Secured routes
+      File: secured-routes
 ---
 Name: Building applications
 Dir: applications

_unused_topics/migrate-from-openshift-sdn.adoc

@@ -37,9 +37,9 @@ include::modules/live-migration-metrics-information.adoc[leveloffset=+3]
 
 * xref:../../networking/network_security/network_policy/about-network-policy.adoc#about-network-policy[About network policy]
 
-* xref:../../networking/changing-cluster-network-mtu.adoc#nw-cluster-mtu-change_changing-cluster-network-mtu[Changing the cluster MTU]
+* xref:../../networking/advanced_networking/changing-cluster-network-mtu.adoc#nw-cluster-mtu-change_changing-cluster-network-mtu[Changing the cluster MTU]
 
-* xref:../../networking/changing-cluster-network-mtu.adoc#mtu-value-selection_changing-cluster-network-mtu[MTU value selection]
+* xref:../../networking/advanced_networking/changing-cluster-network-mtu.adoc#mtu-value-selection_changing-cluster-network-mtu[MTU value selection]
 
 * xref:../../networking/network_security/network_policy/about-network-policy.adoc#nw-networkpolicy-optimize-ovn_about-network-policy[About network policy]
 * OVN-Kubernetes capabilities

applications/deployments/route-based-deployment-strategies.adoc

@@ -35,10 +35,10 @@ include::modules/deployments-ab-testing.adoc[leveloffset=+1]
 include::modules/deployments-ab-testing-lb.adoc[leveloffset=+2]
 
 ifndef::openshift-rosa-hcp[]
-// Remove conditionals when Networking content is in ROSA HCP 
+// Remove conditionals when Networking content is in ROSA HCP
 [role="_additional-resources"]
 [id="additional-resources_{context}"]
 == Additional resources
 
-* xref:../../networking/routes/route-configuration.adoc#nw-route-specific-annotations_route-configuration[Route-specific annotations].
+* xref:../../networking/ingress_load_balancing/routes/route-configuration.adoc#nw-route-specific-annotations_route-configuration[Route-specific annotations].
 endif::[]

architecture/index.adoc

@@ -20,7 +20,7 @@ include::modules/openshift-architecture-common-terms.adoc[leveloffset=+1]
 
 // Topic not included in the OSD/ROSA docs
 ifndef::openshift-dedicated,openshift-rosa[]
-* For more information on networking, see xref:../networking/understanding-networking.adoc#understanding-networking[{product-title} networking].
+* For more information on networking, see xref:../networking/networking_overview/understanding-networking.adoc#understanding-networking[{product-title} networking].
 endif::openshift-dedicated,openshift-rosa[]
 * For more information on storage, see xref:../storage/index.adoc#index[{product-title} storage].
 * For more information on authentication, see xref:../authentication/index.adoc#index[{product-title} authentication].

backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc

@@ -32,7 +32,7 @@ include::modules/manually-restoring-cluster-etcd-backup.adoc[leveloffset=+1]
 
 * xref:../../../installing/installing_bare_metal/upi/installing-bare-metal.adoc#installing-bare-metal[Installing a user-provisioned cluster on bare metal]
 
-* xref:../../../networking/accessing-hosts.adoc#accessing-hosts[Creating a bastion host to access {product-title} instances and the control plane nodes with SSH]
+* xref:../../../networking/networking_overview/accessing-hosts.adoc#accessing-hosts[Creating a bastion host to access {product-title} instances and the control plane nodes with SSH]
 
 * xref:../../../installing/installing_bare_metal/bare-metal-expanding-the-cluster.adoc#replacing-a-bare-metal-control-plane-node_bare-metal-expanding[Replacing a bare-metal control plane node]
 

cicd/builds/setting-up-trusted-ca.adoc

@@ -30,6 +30,6 @@ include::modules/configmap-adding-ca.adoc[leveloffset=+1]
 * link:https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/#create-a-configmap[Create a `ConfigMap`]
 * link:https://kubectl.docs.kubernetes.io/guides/config_management/secrets_configmaps/[Secrets and `ConfigMaps`]
 ifndef::openshift-rosa,openshift-dedicated[]
-* xref:../../networking/configuring-a-custom-pki.adoc#configuring-a-custom-pki[Configuring a custom PKI]
+* xref:../../networking/configuring_network_settings/configuring-a-custom-pki.adoc#configuring-a-custom-pki[Configuring a custom PKI]
 endif::[]
 endif::[]

cicd/pipelines/creating-applications-with-cicd-pipelines.adoc

@@ -86,4 +86,4 @@ include::modules/op-validating-pull-requests-using-GitHub-interceptors.adoc[leve
 * For more examples of reusable tasks, see the link:https://github.com/openshift/pipelines-catalog[OpenShift Catalog] repository. Additionally, you can also see the Tekton Catalog in the Tekton project.
 * To install and deploy a custom instance of Tekton Hub for reusable tasks and pipelines, see xref:../../cicd/pipelines/using-tekton-hub-with-openshift-pipelines.adoc#using-tekton-hub-with-openshift-pipelines[Using {tekton-hub} with {pipelines-title}].
 * For more details on re-encrypt TLS termination, see link:https://docs.openshift.com/container-platform/3.11/architecture/networking/routes.html#re-encryption-termination[Re-encryption Termination].
-* For more details on secured routes, see the xref:../../networking/routes/secured-routes.adoc#secured-routes[Secured routes] section.
+* For more details on secured routes, see the xref:../../networking/ingress_load_balancing/routes/secured-routes.adoc#secured-routes[Secured routes] section.

cicd/pipelines/understanding-openshift-pipelines.adoc

@@ -47,4 +47,4 @@ include::modules/op-about-triggers.adoc[leveloffset=+2]
 * For information on installing {pipelines-shortname}, see xref:../../cicd/pipelines/installing-pipelines.adoc#installing-pipelines[Installing {pipelines-shortname}].
 * For more details on creating custom CI/CD solutions, see xref:../../cicd/pipelines/creating-applications-with-cicd-pipelines.adoc#creating-applications-with-cicd-pipelines[Creating CI/CD solutions for applications using {pipelines-shortname}].
 * For more details on re-encrypt TLS termination, see link:https://docs.openshift.com/container-platform/3.11/architecture/networking/routes.html#re-encryption-termination[Re-encryption Termination].
-* For more details on secured routes, see the xref:../../networking/routes/secured-routes.adoc#secured-routes[Secured routes] section.
+* For more details on secured routes, see the xref:../../networking/ingress_load_balancing/routes/secured-routes.adoc#secured-routes[Secured routes] section.

cicd/pipelines/using-pipelines-as-code.adoc

@@ -86,7 +86,7 @@ include::modules/op-interfacing-pipelines-as-code-with-custom-certificates.adoc[
 
 .Additional resources
 
-* xref:../../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object[Enabling the cluster-wide proxy]
+* xref:../../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object[Enabling the cluster-wide proxy]
 
 include::modules/op-using-repository-crd-with-pipelines-as-code.adoc[leveloffset=+1]
 

cloud_experts_tutorials/cloud-experts-aws-load-balancer-operator.adoc

@@ -23,7 +23,7 @@ include::snippets/mobb-support-statement.adoc[leveloffset=+1]
 ifndef::openshift-rosa-hcp[]
 [TIP]
 ====
-Load Balancers created by the AWS Load Balancer Operator cannot be used for xref:../networking/routes/route-configuration.adoc#route-configuration[OpenShift Routes], and should only be used for individual services or ingress resources that do not need the full layer 7 capabilities of an OpenShift Route.
+Load Balancers created by the AWS Load Balancer Operator cannot be used for xref:../networking/ingress_load_balancing/routes/route-configuration.adoc#route-configuration[OpenShift Routes], and should only be used for individual services or ingress resources that do not need the full layer 7 capabilities of an OpenShift Route.
 ====
 endif::openshift-rosa-hcp[]
 ifdef::openshift-rosa-hcp[]

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-openshift-concepts.adoc

@@ -66,7 +66,7 @@ Similar to the Kubernetes `Ingress` object, Red Hat created the concept of route
 
 [cols="1,1,1"]
 |===
-|Feature | Ingress on OpenShift | Route on OpenShift 
+|Feature | Ingress on OpenShift | Route on OpenShift
 
 |Standard Kubernetes object
 | **X**
@@ -97,23 +97,23 @@ Similar to the Kubernetes `Ingress` object, Red Hat created the concept of route
 | **X**
 
 |TLS re-encryption for improved security
-| 
+|
 | **X**
 
 |TLS passhtrough for improved security
-| 
+|
 | **X**
 
 |Multiple weighted backends (split traffic)
-| 
+|
 | **X**
 
 |Generated pattern-based hostnames
-| 
+|
 | **X**
 
 |Wildcard domains
-| 
+|
 | **X**
 |===
 
@@ -122,12 +122,12 @@ Similar to the Kubernetes `Ingress` object, Red Hat created the concept of route
 DNS resolution for a hostname is handled separately from routing. Your administrator might have configured a cloud domain that will always correctly resolve to the router or modify your unrelated hostname DNS records independently to resolve to the router.
 ====
 
-An individual route can override some defaults by providing specific configurations in its annotations. 
+An individual route can override some defaults by providing specific configurations in its annotations.
 
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/routes/route-configuration.adoc#nw-route-specific-annotations_route-configuration[Route-specific annotations]
+* xref:../../networking/ingress_load_balancing/routes/route-configuration.adoc#nw-route-specific-annotations_route-configuration[Route-specific annotations]
 
 [id="cloud-experts-getting-started-openshift-concepts-imagestreams"]
 == Image streams
@@ -135,7 +135,7 @@ An image stream stores a mapping of tags to images, metadata overrides that are
 
 [id="cloud-experts-getting-started-openshift-concepts-imagestreams-benefits"]
 === Image stream benefits
-Using an image stream makes it easier to change a tag for a container image. Otherwise, to manually change a tag, you must download the image, change it locally, then push it all back. Promoting applications by manually changing a tag and then updating the deployment object entails many steps. 
+Using an image stream makes it easier to change a tag for a container image. Otherwise, to manually change a tag, you must download the image, change it locally, then push it all back. Promoting applications by manually changing a tag and then updating the deployment object entails many steps.
 
 With image streams, you upload a container image once and then you manage its virtual tags internally in OpenShift. In one project you might use the developer tag and only change a reference to it internally, while in production you might use a production tag and also manage it internally. You do not have to deal with the registry.
 

cloud_experts_tutorials/cloud-experts-getting-started/cloud-experts-getting-started-what-is-rosa.adoc

@@ -151,7 +151,7 @@ OpenShift includes the CSI driver for AWS EFS. For more information, see xref:..
 == Using a VPC
 At installation you can select to deploy to an existing VPC or bring your own VPC. You can then select the required subnets and provide a valid CIDR range that encompasses the subnets for the installation program when using those subnets.
 
-ROSA allows multiple clusters to share the same VPC. The number of clusters on one VPC is limited by the remaining AWS resource quota and CIDR ranges that cannot overlap. See xref:../../networking/cidr-range-definitions.adoc#cidr-range-definitions[CIDR Range Definitions] for more information.
+ROSA allows multiple clusters to share the same VPC. The number of clusters on one VPC is limited by the remaining AWS resource quota and CIDR ranges that cannot overlap. See xref:../../networking/networking_overview/cidr-range-definitions.adoc#cidr-range-definitions[CIDR Range Definitions] for more information.
 
 == Network plugin
 ROSA uses the OpenShift OVN-Kubernetes default CNI network provider.

disconnected/updating/disconnected-update-osus.adoc

@@ -112,7 +112,7 @@ include::modules/update-service-configure-cvo.adoc[leveloffset=+1]
 
 [NOTE]
 ====
-See xref:../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy] to configure the CA to trust the update server.
+See xref:../../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy] to configure the CA to trust the update server.
 ====
 
 [id="next-steps_updating-disconnected-cluster-osus_{context}"]

etcd/etcd-backup-restore/etcd-disaster-recovery.adoc

@@ -65,7 +65,7 @@ include::modules/manually-restoring-cluster-etcd-backup.adoc[leveloffset=+2]
 .Additional resources
 * xref:../../backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc#backing-up-etcd-data_backup-etcd[Backing up etcd data]
 * xref:../../installing/installing_bare_metal/upi/installing-bare-metal.adoc#installing-bare-metal[Installing a user-provisioned cluster on bare metal]
-* xref:../../networking/accessing-hosts.adoc#accessing-hosts-on-aws_accessing-hosts[Accessing hosts on Amazon Web Services in an installer-provisioned infrastructure cluster]
+* xref:../../networking/networking_overview/accessing-hosts.adoc#accessing-hosts-on-aws_accessing-hosts[Accessing hosts on Amazon Web Services in an installer-provisioned infrastructure cluster]
 * xref:../../installing/installing_bare_metal/bare-metal-expanding-the-cluster.adoc#replacing-a-bare-metal-control-plane-node_bare-metal-expanding[Replacing a bare-metal control plane node]
 
 include::modules/dr-scenario-cluster-state-issues.adoc[leveloffset=+2]

hosted_control_planes/hcp-deploy/hcp-deploy-bm.adoc

@@ -33,7 +33,7 @@ include::modules/hcp-bm-firewall-port-svc-reqs.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
-* xref:../../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy]
+* xref:../../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy]
 
 include::modules/hcp-bm-infra-reqs.adoc[leveloffset=+2]
 

hosted_control_planes/hcp-networking.adoc

@@ -25,4 +25,4 @@ include::modules/hcp-proxy-addl-network.adoc[leveloffset=+1]
 [id="additional-resources_{context}"]
 == Additional resources
 
-* xref:../networking/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy]
+* xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#enable-cluster-wide-proxy[Configuring the cluster-wide proxy]

hosted_control_planes/hcp-prepare/hcp-requirements.adoc

@@ -14,7 +14,7 @@ The following requirements apply to {hcp}:
 
 * In order to run the HyperShift Operator, your management cluster needs at least three worker nodes.
 
-* You can run both the management cluster and the worker nodes on-premise, such as on a bare-metal platform or on {VirtProductName}. In addition, you can run both the management cluster and the worker nodes on cloud infrastructure, such as {aws-first}. 
+* You can run both the management cluster and the worker nodes on-premise, such as on a bare-metal platform or on {VirtProductName}. In addition, you can run both the management cluster and the worker nodes on cloud infrastructure, such as {aws-first}.
 
 * If you use a mixed infrastructure, such as running the management cluster on {aws-short} and your worker nodes on-premise, or running your worker nodes on {aws-short} and your management cluster on-premise, you must use the `PublicAndPrivate` publishing strategy and follow the latency requirements in the support matrix.
 
@@ -34,4 +34,4 @@ include::modules/hcp-cidr-ranges.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions]
+* xref:../../networking/networking_overview/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions]

installing/installing_aws/ipi/installing-aws-localzone.adoc

@@ -61,11 +61,11 @@ include::modules/edge-machine-pools-aws-local-zones.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../../networking/changing-cluster-network-mtu.adoc#mtu-value-selection_changing-cluster-network-mtu[MTU value selection]
-* xref:../../../networking/changing-cluster-network-mtu.adoc#nw-ovn-ipsec-enable_configuring-ipsec-ovn[Changing the MTU for the cluster network]
+* xref:../../../networking/advanced_networking/changing-cluster-network-mtu.adoc#mtu-value-selection_changing-cluster-network-mtu[MTU value selection]
+* xref:../../../networking/advanced_networking/changing-cluster-network-mtu.adoc#nw-ovn-ipsec-enable_configuring-ipsec-ovn[Changing the MTU for the cluster network]
 * xref:../../../nodes/scheduling/nodes-scheduler-taints-tolerations.adoc#nodes-scheduler-taints-tolerations-about_nodes-scheduler-taints-tolerations[Understanding taints and tolerations]
 * xref:../../../storage/understanding-persistent-storage.adoc#pvc-storage-class_understanding-persistent-storage[Storage classes]
-* xref:../../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc#nw-ingress-sharding_configuring-ingress-cluster-traffic-ingress-controller[Ingress Controller sharding]
+* xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc#nw-ingress-sharding_configuring-ingress-cluster-traffic-ingress-controller[Ingress Controller sharding]
 
 [id="installation-prereqs-aws-local-zone_{context}"]
 == Installation prerequisites

installing/installing_aws/ipi/installing-aws-network-customizations.adoc

@@ -102,7 +102,7 @@ include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
 
 [NOTE]
 ====
-For more information on using a Network Load Balancer (NLB) on AWS, see xref:../../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc#nw-configuring-ingress-cluster-traffic-aws-network-load-balancer_configuring-ingress-cluster-traffic-aws[Configuring Ingress cluster traffic on AWS using a Network Load Balancer].
+For more information on using a Network Load Balancer (NLB) on AWS, see xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc#nw-configuring-ingress-cluster-traffic-aws-network-load-balancer_configuring-ingress-cluster-traffic-aws[Configuring Ingress cluster traffic on AWS using a Network Load Balancer].
 ====
 
 include::modules/nw-aws-nlb-new-cluster.adoc[leveloffset=+1]

installing/installing_aws/ipi/installing-aws-outposts.adoc

@@ -44,7 +44,7 @@ To extend your VPC cluster into an Outpost, you must complete the following netw
 include::modules/nw-cluster-mtu-change.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
-* xref:../../../networking/changing-cluster-network-mtu.adoc#changing-cluster-network-mtu[Changing the MTU for the cluster network]
+* xref:../../../networking/advanced_networking/changing-cluster-network-mtu.adoc#changing-cluster-network-mtu[Changing the MTU for the cluster network]
 
 //Creating subnets for AWS edge compute services
 include::modules/installation-creating-aws-vpc-subnets-edge.adoc[leveloffset=+2]

installing/installing_aws/ipi/installing-aws-wavelength-zone.adoc

@@ -77,11 +77,11 @@ include::modules/edge-machine-pools-aws-local-zones.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../../networking/changing-cluster-network-mtu.adoc#mtu-value-selection_changing-cluster-network-mtu[MTU value selection]
-* xref:../../../networking/changing-cluster-network-mtu.adoc#nw-ovn-ipsec-enable_configuring-ipsec-ovn[Changing the MTU for the cluster network]
+* xref:../../../networking/advanced_networking/changing-cluster-network-mtu.adoc#mtu-value-selection_changing-cluster-network-mtu[MTU value selection]
+* xref:../../../networking/advanced_networking/changing-cluster-network-mtu.adoc#nw-ovn-ipsec-enable_configuring-ipsec-ovn[Changing the MTU for the cluster network]
 * xref:../../../nodes/scheduling/nodes-scheduler-taints-tolerations.adoc#nodes-scheduler-taints-tolerations-about_nodes-scheduler-taints-tolerations[Understanding taints and tolerations]
 * xref:../../../storage/understanding-persistent-storage.adoc#pvc-storage-class_understanding-persistent-storage[Storage classes]
-* xref:../../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc#nw-ingress-sharding_configuring-ingress-cluster-traffic-ingress-controller[Ingress Controller sharding]
+* xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc#nw-ingress-sharding_configuring-ingress-cluster-traffic-ingress-controller[Ingress Controller sharding]
 
 [id="installation-prereqs-aws-wavelength-zone_{context}"]
 == Installation prerequisites

installing/installing_nutanix/installing-nutanix-installer-provisioned.adoc

@@ -24,7 +24,7 @@ In {product-title} version {product-version}, you can choose one of the followin
 ** You configured the firewall to xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[grant access] to the sites that {product-title} requires. This includes the use of Telemetry.
 * If your Nutanix environment is using the default self-signed SSL certificate, replace it with a certificate that is signed by a CA. The installation program requires a valid CA-signed certificate to access to the Prism Central API. For more information about replacing the self-signed certificate, see the  https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_1:mul-security-ssl-certificate-pc-t.html[Nutanix AOS Security Guide].
 +
-If your Nutanix environment uses an internal CA to issue certificates, you must configure a cluster-wide proxy as part of the installation process. For more information, see xref:../../networking/configuring-a-custom-pki.adoc#configuring-a-custom-pki[Configuring a custom PKI].
+If your Nutanix environment uses an internal CA to issue certificates, you must configure a cluster-wide proxy as part of the installation process. For more information, see xref:../../networking/configuring_network_settings/configuring-a-custom-pki.adoc#configuring-a-custom-pki[Configuring a custom PKI].
 +
 [IMPORTANT]
 ====

installing/installing_nutanix/installing-restricted-networks-nutanix-installer-provisioned.adoc

@@ -17,7 +17,7 @@ In {product-title} {product-version}, you can install a cluster on Nutanix infra
 ** You configured the firewall to xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[grant access] to the sites that {product-title} requires. This includes the use of Telemetry.
 * If your Nutanix environment is using the default self-signed SSL/TLS certificate, replace it with a certificate that is signed by a CA. The installation program requires a valid CA-signed certificate to access to the Prism Central API. For more information about replacing the self-signed certificate, see the  https://portal.nutanix.com/page/documents/details?targetId=Nutanix-Security-Guide-v6_1:mul-security-ssl-certificate-pc-t.html[Nutanix AOS Security Guide].
 +
-If your Nutanix environment uses an internal CA to issue certificates, you must configure a cluster-wide proxy as part of the installation process. For more information, see xref:../../networking/configuring-a-custom-pki.adoc#configuring-a-custom-pki[Configuring a custom PKI].
+If your Nutanix environment uses an internal CA to issue certificates, you must configure a cluster-wide proxy as part of the installation process. For more information, see xref:../../networking/configuring_network_settings/configuring-a-custom-pki.adoc#configuring-a-custom-pki[Configuring a custom PKI].
 +
 [IMPORTANT]
 ====

installing/installing_openstack/installing-openstack-installer-custom.adoc

@@ -89,5 +89,5 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
 * If necessary, you can
 xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
-* If you need to enable external access to node ports, xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
+* If you need to enable external access to node ports, xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
 * If you did not configure {rh-openstack} to accept application traffic over floating IP addresses, xref:../../installing/installing_openstack/installing-openstack-network-config.adoc#installation-osp-configuring-api-floating-ip_installing-openstack-network-config[configure {rh-openstack} access with floating IP addresses].

installing/installing_openstack/installing-openstack-installer-ovs-dpdk.adoc

@@ -84,5 +84,5 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
 * If necessary, you can
 xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
-* If you need to enable external access to node ports, xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
+* If you need to enable external access to node ports, xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
 * If you did not configure {rh-openstack} to accept application traffic over floating IP addresses, xref:../../installing/installing_openstack/installing-openstack-network-config.adoc#installation-osp-configuring-api-floating-ip_installing-openstack-network-config[configure {rh-openstack} access with floating IP addresses].

installing/installing_openstack/installing-openstack-user-sr-iov.adoc

@@ -100,5 +100,5 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
 * If necessary, you can
 xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
-* If you need to enable external access to node ports, xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
+* If you need to enable external access to node ports, xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
 * If you did not configure {rh-openstack} to accept application traffic over floating IP addresses, xref:../../installing/installing_openstack/installing-openstack-network-config.adoc#installation-osp-configuring-api-floating-ip_installing-openstack-network-config[configure {rh-openstack} access with floating IP addresses].

installing/installing_openstack/installing-openstack-user.adoc

@@ -86,5 +86,5 @@ include::modules/cluster-telemetry.adoc[leveloffset=+1]
 * xref:../../post_installation_configuration/cluster-tasks.adoc#available_cluster_customizations[Customize your cluster].
 * If necessary, you can
 xref:../../support/remote_health_monitoring/opting-out-of-remote-health-reporting.adoc#opting-out-remote-health-reporting_opting-out-remote-health-reporting[opt out of remote health reporting].
-* If you need to enable external access to node ports, xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
+* If you need to enable external access to node ports, xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#nw-using-nodeport_configuring-ingress-cluster-traffic-nodeport[configure ingress cluster traffic by using a node port].
 * If you did not configure {rh-openstack} to accept application traffic over floating IP addresses, xref:../../installing/installing_openstack/installing-openstack-network-config.adoc#installation-osp-configuring-api-floating-ip_installing-openstack-network-config[configure {rh-openstack} access with floating IP addresses].

machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-aws.adoc

@@ -30,7 +30,7 @@ include::modules/private-clusters-setting-api-private.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
-* xref:../../../networking/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc#nw-ingresscontroller-change-internal_nw-configuring-ingress-controller-endpoint-publishing-strategy[Configuring the Ingress Controller endpoint publishing scope to Internal]
+* xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc#nw-ingresscontroller-change-internal_nw-configuring-ingress-controller-endpoint-publishing-strategy[Configuring the Ingress Controller endpoint publishing scope to Internal]
 
 //Selecting a larger Amazon Web Services instance type for control plane machines
 include::modules/cpms-changing-aws-instance-type.adoc[leveloffset=+2]

machine_management/control_plane_machine_management/cpmso_provider_configurations/cpmso-config-options-azure.adoc

@@ -28,7 +28,7 @@ You can enable features by updating values in the control plane machine set.
 include::modules/private-clusters-setting-api-private.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
-* xref:../../../networking/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc#nw-ingresscontroller-change-internal_nw-configuring-ingress-controller-endpoint-publishing-strategy[Configuring the Ingress Controller endpoint publishing scope to Internal]
+* xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc#nw-ingresscontroller-change-internal_nw-configuring-ingress-controller-endpoint-publishing-strategy[Configuring the Ingress Controller endpoint publishing scope to Internal]
 
 //Using the Azure Marketplace offering
 include::modules/installation-azure-marketplace-subscribe.adoc[leveloffset=+2]

machine_management/manually-scaling-machineset.adoc

@@ -15,7 +15,7 @@ If you need to modify aspects of a compute machine set outside of scaling, see x
 
 == Prerequisites
 
-* If you enabled the cluster-wide proxy and scale up compute machines not included in `networking.machineNetwork[].cidr` from the installation configuration, you must xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[add the compute machines to the Proxy object's `noProxy` field] to prevent connection issues.
+* If you enabled the cluster-wide proxy and scale up compute machines not included in `networking.machineNetwork[].cidr` from the installation configuration, you must xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[add the compute machines to the Proxy object's `noProxy` field] to prevent connection issues.
 
 include::snippets/machine-user-provisioned-limitations.adoc[leveloffset=+1]
 

migrating_from_ocp_3_to_4/index.adoc

@@ -14,7 +14,7 @@ Before migrating from {product-title} 3 to 4, you can check xref:../migrating_fr
 
 * xref:../architecture/architecture.adoc#architecture[Architecture]
 * xref:../architecture/architecture-installation.adoc#architecture-installation[Installation and update]
-* xref:../storage/index.adoc#index[Storage], xref:../networking/understanding-networking.adoc#understanding-networking[network], xref:../security/index.adoc#index[security], and xref:../observability/monitoring/about-ocp-monitoring/about-ocp-monitoring.adoc#about-ocp-monitoring[monitoring considerations]
+* xref:../storage/index.adoc#index[Storage], xref:../networking/networking_overview/understanding-networking.adoc#understanding-networking[network], xref:../security/index.adoc#index[security], and xref:../observability/monitoring/about-ocp-monitoring/about-ocp-monitoring.adoc#about-ocp-monitoring[monitoring considerations]
 
 [id="mtc-3-to-4-overview-planning-network-considerations-mtc"]
 == Planning network considerations

migrating_from_ocp_3_to_4/installing-3-4.adoc

@@ -23,7 +23,7 @@ include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
 include::modules/migration-about-configuring-proxies.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+2]
 
-For more information, see xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
+For more information, see xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
 
 [id="configuring-replication-repository_{context}"]
 == Configuring a replication repository

migrating_from_ocp_3_to_4/installing-restricted-3-4.adoc

@@ -27,7 +27,7 @@ include::modules/migration-installing-legacy-operator.adoc[leveloffset=+1]
 include::modules/migration-about-configuring-proxies.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+2]
 
-For more information, see xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
+For more information, see xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
 
 [id="configuring-replication-repository_{context}"]
 == Configuring a replication repository

migration_toolkit_for_containers/installing-mtc-restricted.adoc

@@ -35,7 +35,7 @@ include::modules/migration-installing-legacy-operator.adoc[leveloffset=+1]
 include::modules/migration-about-configuring-proxies.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+2]
 
-For more information, see xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
+For more information, see xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
 
 [id="migration-rsync-root-non-root_{context}"]
 == Running Rsync as either root or non-root

migration_toolkit_for_containers/installing-mtc.adoc

@@ -26,7 +26,7 @@ include::modules/migration-installing-mtc-on-ocp-4.adoc[leveloffset=+1]
 include::modules/migration-about-configuring-proxies.adoc[leveloffset=+1]
 include::modules/migration-configuring-proxies.adoc[leveloffset=+2]
 
-For more information, see xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
+For more information, see xref:../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[Configuring the cluster-wide proxy].
 
 include::modules/ocp-running-rsync-root-or-non-root.adoc[leveloffset=+2]
 

modules/rosa-hcp-sts-creating-a-cluster-cli-no-cni-plugin.adoc

@@ -24,7 +24,7 @@ When using the {product-title} (ROSA) command-line interface (CLI), `rosa`, to c
 +
 [NOTE]
 ====
-When creating a {hcp-title} cluster, the default machine Classless Inter-Domain Routing (CIDR) is `10.0.0.0/16`. If this does not correspond to the CIDR range for your VPC subnets, add `--machine-cidr <address_block>` to the following commands. To learn more about the default CIDR ranges for {product-title}, see xref:../networking/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions].
+When creating a {hcp-title} cluster, the default machine Classless Inter-Domain Routing (CIDR) is `10.0.0.0/16`. If this does not correspond to the CIDR range for your VPC subnets, add `--machine-cidr <address_block>` to the following commands. To learn more about the default CIDR ranges for {product-title}, see xref:../networking/networking_overview/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions].
 ====
 +
 ** Create a cluster with a single, initial machine pool, publicly available API, publicly available Ingress, and no CNI plugin by running the following command:
@@ -60,7 +60,7 @@ $ rosa describe cluster --cluster=<cluster_name>
 +
 [IMPORTANT]
 ====
-When you first log in to the cluster after it reaches `ready` status, the nodes will still be in the `not ready` state until you install your own CNI plugin. After CNI installation, the nodes will change to `ready`. 
+When you first log in to the cluster after it reaches `ready` status, the nodes will still be in the `not ready` state until you install your own CNI plugin. After CNI installation, the nodes will change to `ready`.
 ====
 +
 The following `State` field changes are listed in the output as the cluster installation progresses:

networking/advanced_networking/changing-cluster-network-mtu.adoc

@@ -10,12 +10,13 @@ toc::[]
 As a cluster administrator, you can change the MTU for the cluster network after cluster installation. This change is disruptive as cluster nodes must be rebooted to finalize the MTU change.
 
 include::modules/nw-cluster-mtu-change-about.adoc[leveloffset=+1]
+
 include::modules/nw-cluster-mtu-change.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 [id="{context}-additional-resources"]
 == Additional resources
 
-* xref:../installing/installing_bare_metal/upi/installing-bare-metal.adoc#installation-user-infra-machines-advanced_network_installing-bare-metal[Using advanced networking options for PXE and ISO installations]
+* xref:../../installing/installing_bare_metal/upi/installing-bare-metal.adoc#installation-user-infra-machines-advanced_network_installing-bare-metal[Using advanced networking options for PXE and ISO installations]
 * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index#proc_manually-creating-a-networkmanager-profile-in-keyfile-format_assembly_networkmanager-connection-profiles-in-keyfile-format[Manually creating NetworkManager profiles in key file format]
 * link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/configuring_and_managing_networking/index#configuring-a-dynamic-ethernet-connection-using-nmcli_configuring-an-ethernet-connection[Configuring a dynamic Ethernet connection using nmcli]

networking/advanced_networking/ptp/about-ptp.adoc

@@ -32,7 +32,7 @@ include::modules/nw-ptp-introduction.adoc[leveloffset=+1]
 
 [IMPORTANT]
 ====
-Before enabling PTP, ensure that NTP is disabled for the required nodes. You can disable the chrony time service (`chronyd`) using a `MachineConfig` custom resource. For more information, see xref:../../machine_configuration/machine-configs-configure.adoc#cnf-disable-chronyd_machine-configs-configure[Disabling chrony time service].
+Before enabling PTP, ensure that NTP is disabled for the required nodes. You can disable the chrony time service (`chronyd`) using a `MachineConfig` custom resource. For more information, see xref:../../../machine_configuration/machine-configs-configure.adoc#cnf-disable-chronyd_machine-configs-configure[Disabling chrony time service].
 ====
 
 include::modules/ptp-linuxptp-introduction.adoc[leveloffset=+1]

networking/advanced_networking/ptp/configuring-ptp.adoc

@@ -32,7 +32,7 @@ include::modules/nw-ptp-configuring-linuxptp-services-as-grandmaster-clock-three
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
+* xref:../../../networking/advanced_networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
 
 include::modules/nw-ptp-grandmaster-clock-configuration-reference.adoc[leveloffset=+1]
 
@@ -49,7 +49,7 @@ include::modules/nw-ptp-holdover-in-a-grandmaster-clock.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/configuring-ptp.adoc#nw-ptp-grandmaster-clock-class-reference_configuring-ptp[Grandmaster clock class sync state reference]
+* xref:../../../networking/advanced_networking/ptp/configuring-ptp.adoc#nw-ptp-grandmaster-clock-class-reference_configuring-ptp[Grandmaster clock class sync state reference]
 
 include::modules/ptp-configuring-dynamic-leap-seconds-handling-for-tgm.adoc[leveloffset=+1]
 
@@ -58,9 +58,9 @@ include::modules/nw-ptp-configuring-linuxptp-services-as-boundary-clock.adoc[lev
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/configuring-ptp.adoc#cnf-configuring-fifo-priority-scheduling-for-ptp_configuring-ptp[Configuring FIFO priority scheduling for PTP hardware]
+* xref:../../../networking/advanced_networking/ptp/configuring-ptp.adoc#cnf-configuring-fifo-priority-scheduling-for-ptp_configuring-ptp[Configuring FIFO priority scheduling for PTP hardware]
 
-* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
+* xref:../../../networking/advanced_networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
 
 include::modules/ptp-configuring-linuxptp-services-as-boundary-clock-dual-nic.adoc[leveloffset=+2]
 
@@ -71,9 +71,9 @@ include::modules/nw-ptp-configuring-linuxptp-services-as-ordinary-clock.adoc[lev
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/configuring-ptp.adoc#cnf-configuring-fifo-priority-scheduling-for-ptp_configuring-ptp[Configuring FIFO priority scheduling for PTP hardware]
+* xref:../../../networking/advanced_networking/ptp/configuring-ptp.adoc#cnf-configuring-fifo-priority-scheduling-for-ptp_configuring-ptp[Configuring FIFO priority scheduling for PTP hardware]
 
-* xref:../../networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
+* xref:../../../networking/advanced_networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc#cnf-configuring-the-ptp-fast-event-publisher-v2_ptp-consumer[Configuring the PTP fast event notifications publisher]
 
 include::modules/nw-columbiaville-ptp-config-refererence.adoc[leveloffset=+2]
 
@@ -82,9 +82,9 @@ include::modules/nw-ptp-configuring-linuxptp-services-dual-port-oc.adoc[leveloff
 [role="_additional-resources"]
 .Additional resources
 
-* For a complete example CR that configures `linuxptp` services as an ordinary clock with PTP fast events, see xref:../../networking/ptp/configuring-ptp.adoc#configuring-linuxptp-services-as-ordinary-clock_configuring-ptp[Configuring linuxptp services as ordinary clock].
+* For a complete example CR that configures `linuxptp` services as an ordinary clock with PTP fast events, see xref:../../../networking/advanced_networking/ptp/configuring-ptp.adoc#configuring-linuxptp-services-as-ordinary-clock_configuring-ptp[Configuring linuxptp services as ordinary clock].
 
-* xref:../../networking/ptp/about-ptp.adoc#ptp-dual-ports-oc_about-ptp[Using dual-port NICs to improve redundancy for PTP ordinary clocks]
+* xref:../../../networking/advanced_networking/ptp/about-ptp.adoc#ptp-dual-ports-oc_about-ptp[Using dual-port NICs to improve redundancy for PTP ordinary clocks]
 
 include::modules/cnf-configuring-fifo-priority-scheduling-for-ptp.adoc[leveloffset=+1]
 

networking/advanced_networking/ptp/ptp-cloud-events-consumer-dev-reference-v2.adoc

@@ -19,7 +19,7 @@ A complete events consumer application example is outside the scope of this info
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/ptp-events-rest-api-reference-v2.adoc#ptp-events-rest-api-reference-v2[PTP events REST API v2 reference]
+* xref:../../../networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc#ptp-events-rest-api-reference-v2[PTP events REST API v2 reference]
 
 include::modules/cnf-about-ptp-fast-event-notifications-framework.adoc[leveloffset=+1]
 
@@ -30,7 +30,7 @@ include::modules/cnf-configuring-the-ptp-fast-event-publisher.adoc[leveloffset=+
 [role="_additional-resources"]
 .Additional resources
 
-* For a complete example CR that configures `linuxptp` services as an ordinary clock with PTP fast events, see xref:../../networking/ptp/configuring-ptp.adoc#configuring-linuxptp-services-as-ordinary-clock_configuring-ptp[Configuring linuxptp services as ordinary clock].
+* For a complete example CR that configures `linuxptp` services as an ordinary clock with PTP fast events, see xref:../../../networking/advanced_networking/ptp/configuring-ptp.adoc#configuring-linuxptp-services-as-ordinary-clock_configuring-ptp[Configuring linuxptp services as ordinary clock].
 
 include::modules/ptp-events-consumer-application-v2.adoc[leveloffset=+1]
 
@@ -41,7 +41,7 @@ include::modules/ptp-subscribing-consumer-app-to-events.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloud-notifications-v2-subscriptions_using-ptp-hardware-fast-events-framework-v2[api/ocloudNotifications/v2/subscriptions]
+* xref:../../../networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloud-notifications-v2-subscriptions_using-ptp-hardware-fast-events-framework-v2[api/ocloudNotifications/v2/subscriptions]
 
 include::modules/ptp-verifying-events-consumer-app-is-receiving-events-v2.adoc[leveloffset=+1]
 
@@ -50,6 +50,6 @@ include::modules/cnf-monitoring-fast-events-metrics.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../observability/monitoring/accessing-metrics/accessing-metrics-as-a-developer.adoc#accessing-metrics-as-a-developer[Accessing metrics as a developer]
+* xref:../../../observability/monitoring/accessing-metrics/accessing-metrics-as-a-developer.adoc#accessing-metrics-as-a-developer[Accessing metrics as a developer]
 
 include::modules/nw-ptp-operator-metrics-reference.adoc[leveloffset=+1]

networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc

@@ -8,22 +8,22 @@ toc::[]
 
 Use the following REST API v2 endpoints to subscribe the `cloud-event-consumer` application to Precision Time Protocol (PTP) events posted at `\http://ptp-event-publisher-service-NODE_NAME.openshift-ptp.svc.cluster.local:9043/api/ocloudNotifications/v2` in the PTP events producer pod.
 
-* xref:../../networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloud-notifications-v2-subscriptions_{context}[`api/ocloudNotifications/v2/subscriptions`]
+* xref:../../networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloud-notifications-v2-subscriptions_{context}[`api/ocloudNotifications/v2/subscriptions`]
 ** `POST`: Creates a new subscription
 ** `GET`: Retrieves a list of subscriptions
 ** `DELETE`: Deletes all subscriptions
 
-* xref:../../networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloud-notifications-v2-subscriptions-subscription_id_{context}[`api/ocloudNotifications/v2/subscriptions/{subscription_id}`]
+* xref:../../networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloud-notifications-v2-subscriptions-subscription_id_{context}[`api/ocloudNotifications/v2/subscriptions/{subscription_id}`]
 ** `GET`: Returns details for the specified subscription ID
 ** `DELETE`: Deletes the subscription associated with the specified subscription ID
 
-* xref:../../networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloudnotifications-v2-health_{context}[`api/ocloudNotifications/v2/health`]
+* xref:../../networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloudnotifications-v2-health_{context}[`api/ocloudNotifications/v2/health`]
 ** `GET`: Returns the health status of `ocloudNotifications` API
 
-* xref:../../networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloudnotifications-v2-publishers_{context}[`api/ocloudNotifications/v2/publishers`]
+* xref:../../networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc#api-ocloudnotifications-v2-publishers_{context}[`api/ocloudNotifications/v2/publishers`]
 ** `GET`: Returns a list of PTP event publishers for the cluster node
 
-* xref:../../networking/ptp/ptp-events-rest-api-reference-v2.adoc#resource-address-current-state-v2_{context}[`api/ocloudnotifications/v2/{resource_address}/CurrentState`]
+* xref:../../networking/advanced_networking/ptp/ptp-events-rest-api-reference-v2.adoc#resource-address-current-state-v2_{context}[`api/ocloudnotifications/v2/{resource_address}/CurrentState`]
 ** `GET`: Returns the current state of the event type specified by the `{resouce_address}`.
 
 include::modules/cnf-fast-event-notifications-api-reference-v2.adoc[leveloffset=+1]

networking/advanced_networking/snippets

@@ -0,0 +1 @@
+../../snippets

networking/configuring-cluster-wide-proxy.adoc

@@ -54,6 +54,7 @@ ifdef::openshift-rosa[]
 You can configure an HTTP or HTTPS proxy when you install a {product-title} (ROSA) cluster into an existing Virtual Private Cloud (VPC). You can configure the proxy during installation by using {cluster-manager-first} or the ROSA CLI (`rosa`).
 
 include::modules/configuring-a-proxy-during-installation-ocm.adoc[leveloffset=+2]
+
 include::modules/configuring-a-proxy-during-installation-cli.adoc[leveloffset=+2]
 endif::openshift-rosa[]
 
@@ -81,6 +82,7 @@ ifdef::openshift-rosa[]
 You can configure an HTTP or HTTPS proxy after you install a {product-title} (ROSA) cluster into an existing Virtual Private Cloud (VPC). You can configure the proxy after installation by using {cluster-manager-first} or the ROSA CLI (`rosa`).
 
 include::modules/configuring-a-proxy-after-installation-ocm.adoc[leveloffset=+2]
+
 include::modules/configuring-a-proxy-after-installation-cli.adoc[leveloffset=+2]
 
 [id="removing-cluster-wide-proxy_{context}"]
@@ -89,5 +91,6 @@ include::modules/configuring-a-proxy-after-installation-cli.adoc[leveloffset=+2]
 You can remove your cluster-wide proxy by using the ROSA CLI. After removing the cluster, you should also remove any trust bundles that are added to the cluster.
 
 include::modules/nw-rosa-proxy-remove-cli.adoc[leveloffset=+2]
+
 include::modules/configmap-removing-ca.adoc[leveloffset=+2]
 endif::openshift-rosa[]

networking/configuring_network_settings/configure-syscontrols-interface-tuning-cni.adoc

@@ -20,6 +20,6 @@ include::modules/nw-cfg-config-all-multi-cni.adoc[leveloffset=+1]
 [id="additional-resources_nodes-setting-interface-level-network-sysctls"]
 == Additional resources
 
-* xref:../nodes/containers/nodes-containers-sysctls.adoc#nodes-containers-sysctls[Using sysctls in containers]
-* xref:../networking/hardware_networks/configuring-sriov-device.adoc#nw-sriov-networknodepolicy-object_configuring-sriov-device[SR-IOV network node configuration object]
-* xref:../networking/hardware_networks/configuring-interface-sysctl-sriov-device.adoc#configuring-interface-level-sysctl-settings-sriov-device[Configuring interface-level network sysctl settings and all-multicast mode for SR-IOV networks]
+* xref:../../nodes/containers/nodes-containers-sysctls.adoc#nodes-containers-sysctls[Using sysctls in containers]
+* xref:../../networking/hardware_networks/configuring-sriov-device.adoc#nw-sriov-networknodepolicy-object_configuring-sriov-device[SR-IOV network node configuration object]
+* xref:../../networking/hardware_networks/configuring-interface-sysctl-sriov-device.adoc#configuring-interface-level-sysctl-settings-sriov-device[Configuring interface-level network sysctl settings and all-multicast mode for SR-IOV networks]

networking/configuring_network_settings/configuring-a-custom-pki.adoc

@@ -14,7 +14,7 @@ its privately signed CA certificates are recognized across the cluster.
 You can leverage the Proxy API to add cluster-wide trusted CA certificates. You
 must do this either during installation or at runtime.
 
-* During _installation_, xref:../networking/configuring-a-custom-pki.adoc#installation-configure-proxy_{context}[configure the cluster-wide proxy]. You must define your
+* During _installation_, xref:../networking/configuring_network_settings/configuring-a-custom-pki.adoc#installation-configure-proxy_{context}[configure the cluster-wide proxy]. You must define your
 privately signed CA certificates in the `install-config.yaml` file's
 `additionalTrustBundle` setting.
 +
@@ -24,7 +24,7 @@ Operator then creates a `trusted-ca-bundle` ConfigMap that merges these CA
 certificates with the {op-system-first} trust bundle; this ConfigMap is
 referenced in the Proxy object's `trustedCA` field.
 
-* At _runtime_, xref:../networking/configuring-a-custom-pki.adoc#nw-proxy-configure-object_{context}[modify the default Proxy object to include your privately signed CA certificates] (part of cluster's proxy enablement workflow). This involves
+* At _runtime_, xref:../networking/configuring_network_settings/configuring-a-custom-pki.adoc#nw-proxy-configure-object_{context}[modify the default Proxy object to include your privately signed CA certificates] (part of cluster's proxy enablement workflow). This involves
 creating a ConfigMap that contains the privately signed CA certificates that
 should be trusted by the cluster, and then modifying the proxy resource with the
 `trustedCA` referencing the privately signed certificates' ConfigMap.

networking/configuring_network_settings/configuring-cluster-network-range.adoc

@@ -10,7 +10,7 @@ As a cluster administrator, you can expand the cluster network range after clust
 
 For example, if you deployed a cluster and specified `10.128.0.0/19` as the cluster network range and a host prefix of `23`, you are limited to 16 nodes. You can expand that to 510 nodes by changing the CIDR mask on a cluster to `/14`.
 
-When expanding the cluster network address range, your cluster must use the xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[OVN-Kubernetes network plugin]. Other network plugins are not supported.
+When expanding the cluster network address range, your cluster must use the xref:../../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[OVN-Kubernetes network plugin]. Other network plugins are not supported.
 
 The following limitations apply when modifying the cluster network IP address range:
 
@@ -25,4 +25,4 @@ include::modules/nw-cluster-network-range-edit.adoc[leveloffset=+1]
 == Additional resources
 
 * link:https://access.redhat.com/labs/ocpnc/[Red Hat OpenShift Network Calculator]
-* xref:../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[About the OVN-Kubernetes network plugin]
+* xref:../../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[About the OVN-Kubernetes network plugin]

networking/configuring_network_settings/configuring-ipfailover.adoc

@@ -69,7 +69,7 @@ include::modules/nw-ipfailover-cluster-ha-ingress.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
-* xref:../networking/configuring_ingress_cluster_traffic/configuring-externalip.adoc#configuration-externalip_configuring-externalip[Configuration for ExternalIP]
+* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-externalip.adoc#configuration-externalip_configuring-externalip[Configuration for ExternalIP]
 
 * link:https://kubernetes.io/docs/concepts/services-networking/service/#external-ips[Kubernetes documentation on ExternalIP]
 

networking/configuring_network_settings/configuring-node-port-service-range.adoc

@@ -10,7 +10,7 @@ During cluster installation, you can configure the node port range to meet the r
 
 [IMPORTANT]
 ====
-Before you expand a node port range, consider that Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify the expanding node port range does not impact your cluster. If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it. 
+Before you expand a node port range, consider that Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify the expanding node port range does not impact your cluster. If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it.
 ====
 
 If you do not set a node port range during cluster installation, the default range of `30000-32768` applies to your cluster. In this situation, you can expand the range on either side, but you must preserve `30000-32768` within your new port range.
@@ -28,6 +28,6 @@ include::modules/nw-nodeport-service-range-edit.adoc[leveloffset=+1]
 [id="configuring-node-port-service-range-additional-resources"]
 == Additional resources
 
-* xref:../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#configuring-ingress-cluster-traffic-nodeport[Configuring ingress cluster traffic using a NodePort]
-* xref:../rest_api/config_apis/network-config-openshift-io-v1.adoc#network-config-openshift-io-v1[Network [config.openshift.io/v1]]
-* xref:../rest_api/network_apis/service-v1.adoc#service-v1[Service [core/v1]]
+* xref:../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#configuring-ingress-cluster-traffic-nodeport[Configuring ingress cluster traffic using a NodePort]
+* xref:../../rest_api/config_apis/network-config-openshift-io-v1.adoc#network-config-openshift-io-v1[Network [config.openshift.io/v1]]
+* xref:../../rest_api/network_apis/service-v1.adoc#service-v1[Service [core/v1]]

networking/configuring_network_settings/enable-cluster-wide-proxy.adoc

@@ -6,9 +6,9 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Production environments can deny direct access to the internet and instead have an HTTP or HTTPS proxy available. You can configure {product-title} to use a proxy by xref:../networking/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[modifying the Proxy object for existing clusters] or by configuring the proxy settings in the `install-config.yaml` file for new clusters.
+Production environments can deny direct access to the internet and instead have an HTTP or HTTPS proxy available. You can configure {product-title} to use a proxy by xref:../../networking/configuring_network_settings/enable-cluster-wide-proxy.adoc#nw-proxy-configure-object_config-cluster-wide-proxy[modifying the Proxy object for existing clusters] or by configuring the proxy settings in the `install-config.yaml` file for new clusters.
 
-After you enable a cluster-wide egress proxy for your cluster on a supported platform, {op-system-first} populates the `status.noProxy` parameter with the values of the `networking.machineNetwork[].cidr`, `networking.clusterNetwork[].cidr`, and `networking.serviceNetwork[]` fields from your `install-config.yaml` file that exists on the supported platform. 
+After you enable a cluster-wide egress proxy for your cluster on a supported platform, {op-system-first} populates the `status.noProxy` parameter with the values of the `networking.machineNetwork[].cidr`, `networking.clusterNetwork[].cidr`, and `networking.serviceNetwork[]` fields from your `install-config.yaml` file that exists on the supported platform.
 
 [NOTE]
 ====
@@ -47,7 +47,7 @@ status:
 <1> Specify IP address blocks from which pod IP addresses are allocated. The default value is `10.128.0.0/14` with a host prefix of `/23`.
 <2> Specify the IP address blocks for machines. The default value is `10.0.0.0/16`.
 <3> Specify IP address block for services. The default value is `172.30.0.0/16`.
-<4> You can find the URL of the internal API server by running the `oc get infrastructures.config.openshift.io cluster -o jsonpath='{.status.etcdDiscoveryDomain}'` command. 
+<4> You can find the URL of the internal API server by running the `oc get infrastructures.config.openshift.io cluster -o jsonpath='{.status.etcdDiscoveryDomain}'` command.
 
 [IMPORTANT]
 ====
@@ -57,7 +57,7 @@ If your installation type does not include setting the `networking.machineNetwor
 [id="prerequisites_cluster-wide-proxy"]
 == Prerequisites
 
-Review the xref:../installing/install_config/configuring-firewall.adoc#configuring-firewall[sites that your cluster requires access to] and determine whether any of them must bypass the proxy. By default, all cluster system egress traffic is proxied, including calls to the cloud provider API for the cloud that hosts your cluster. The system-wide proxy affects system components only, not user workloads. If necessary, add sites to the `spec.noProxy` parameter of the `Proxy` object to bypass the proxy.
+Review the xref:../../installing/install_config/configuring-firewall.adoc#configuring-firewall[sites that your cluster requires access to] and determine whether any of them must bypass the proxy. By default, all cluster system egress traffic is proxied, including calls to the cloud provider API for the cloud that hosts your cluster. The system-wide proxy affects system components only, not user workloads. If necessary, add sites to the `spec.noProxy` parameter of the `Proxy` object to bypass the proxy.
 
 // Enabling the cluster-wide proxy
 include::modules/nw-proxy-configure-object.adoc[leveloffset=+1]
@@ -72,7 +72,7 @@ include::modules/nw-verify-proxy-configuration.adoc[leveloffset=+1]
 [role="_additional-resources"]
 == Additional resources
 
-* xref:../networking/configuring-cluster-network-range.adoc#configuring-cluster-network-range[Configuring the cluster network range]
-* xref:../security/certificates/updating-ca-bundle.adoc#ca-bundle-understanding_updating-ca-bundle[Understanding the CA Bundle certificate]
-* xref:../security/certificate_types_descriptions/proxy-certificates.adoc#customization[Proxy certificates]
+* xref:../../networking/configuring_network_settings/configuring-cluster-network-range.adoc#configuring-cluster-network-range[Configuring the cluster network range]
+* xref:../../security/certificates/updating-ca-bundle.adoc#ca-bundle-understanding_updating-ca-bundle[Understanding the CA Bundle certificate]
+* xref:../../security/certificate_types_descriptions/proxy-certificates.adoc#customization[Proxy certificates]
 * link:https://access.redhat.com/solutions/7065528[How is the cluster-wide proxy setting applied to {product-title} nodes?]

networking/configuring_network_settings/snippets

@@ -0,0 +1 @@
+../../snippets

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/_attributes

@@ -0,0 +1 @@
+../../_attributes/

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-externalip.adoc

@@ -20,9 +20,9 @@ include::modules/nw-externalip-about.adoc[leveloffset=+1]
 [id="additional-resources_{context}"]
 == Additional resources
 
-* xref:../../networking/configuring-ipfailover.adoc#configuring-ipfailover[Configuring IP failover]
+* xref:../../../networking/configuring_network_settings/configuring-ipfailover.adoc#configuring-ipfailover[Configuring IP failover]
 
-* xref:../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator]
+* xref:../../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator]
 
 // Configuration for ExternalIP
 include::modules/configuration-externalip.adoc[leveloffset=+1]
@@ -42,4 +42,4 @@ include::modules/nw-externalip-configuring.adoc[leveloffset=+1]
 [id="configuring-externalip-next-steps"]
 == Next steps
 
-* xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-service-external-ip.adoc#configuring-ingress-cluster-traffic-service-external-ip[Configuring ingress cluster traffic for a service external IP]
+* xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-service-external-ip.adoc#configuring-ingress-cluster-traffic-service-external-ip[Configuring ingress cluster traffic for a service external IP]

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc

@@ -35,7 +35,7 @@ include::modules/nw-aws-nlb-existing-cluster.adoc[leveloffset=+2]
 
 [IMPORTANT]
 ====
-Before you can configure an Ingress Controller NLB on a new AWS cluster, you must complete the xref:../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installation-initializing_installing-aws-network-customizations[Creating the installation configuration file] procedure.
+Before you can configure an Ingress Controller NLB on a new AWS cluster, you must complete the xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installation-initializing_installing-aws-network-customizations[Creating the installation configuration file] procedure.
 ====
 
 include::modules/nw-aws-nlb-new-cluster.adoc[leveloffset=+2]
@@ -50,6 +50,6 @@ include::modules/nw-ingress-aws-static-eip-nlb-configuration.adoc[leveloffset=+2
 [id="additional-resources_configuring-ingress-cluster-traffic-aws"]
 == Additional resources
 
-* xref:../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-network-customizations[Installing a cluster on AWS with network customizations].
+* xref:../../../installing/installing_aws/ipi/installing-aws-network-customizations.adoc#installing-aws-network-customizations[Installing a cluster on AWS with network customizations].
 * For more information on support for NLBs, see link:https://kubernetes.io/docs/concepts/services-networking/service/#aws-nlb-support[Network Load Balancer support on AWS].
 * For more information on proxy protocol support for CLBs, see link:https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-proxy-protocol.html[Configure proxy protocol support for your Classic Load Balancer]

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

@@ -77,13 +77,13 @@ include::modules/nw-ingress-sharding-route-configuration.adoc[leveloffset=+2]
 [id="additional-resources_ingress-sharding"]
 === Additional resources
 
-* xref:../../scalability_and_performance/optimization/routing-optimization.adoc#baseline-router-performance_routing-optimization[Baseline Ingress Controller (router) performance]
+* xref:../../../scalability_and_performance/optimization/routing-optimization.adoc#baseline-router-performance_routing-optimization[Baseline Ingress Controller (router) performance]
 
-* xref:../../networking/networking_operators/ingress-operator.adoc#configuring-ingress-controller[Configuring the Ingress Controller]
+* xref:../../../networking/networking_operators/ingress-operator.adoc#configuring-ingress-controller[Configuring the Ingress Controller]
 
-* xref:../../installing/installing_bare_metal/upi/installing-bare-metal.adoc#installing-bare-metal[Installing a cluster on bare metal]
+* xref:../../../installing/installing_bare_metal/upi/installing-bare-metal.adoc#installing-bare-metal[Installing a cluster on bare metal]
 
-* xref:../../installing/installing_vsphere/upi/installing-vsphere.adoc#installing-vsphere[Installing a cluster on vSphere]
+* xref:../../../installing/installing_vsphere/upi/installing-vsphere.adoc#installing-vsphere[Installing a cluster on vSphere]
 
-* xref:../../networking/network_security/network_policy/about-network-policy.adoc#about-network-policy[About network policy]
+* xref:../../../networking/network_security/network_policy/about-network-policy.adoc#about-network-policy[About network policy]
 endif::openshift-enterprise,openshift-webscale,openshift-origin[]

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer-allowed-source-ranges.adoc

@@ -9,8 +9,9 @@ toc::[]
 You can specify a list of IP address ranges for the `IngressController`. This restricts access to the load balancer service when the `endpointPublishingStrategy` is `LoadBalancerService`.
 
 include::modules/nw-configuring-lb-allowed-source-ranges.adoc[leveloffset=+1]
+
 include::modules/nw-configuring-lb-allowed-source-ranges-migration.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 == Additional resources
-* xref:../../updating/understanding_updates/intro-to-updates.adoc#understanding-openshift-updates[Introduction to OpenShift updates]
+* xref:../../../updating/understanding_updates/intro-to-updates.adoc#understanding-openshift-updates[Introduction to OpenShift updates]

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc

@@ -38,7 +38,7 @@ procedure assumes that the external system is on the same subnet as the cluster.
 The additional networking required for external systems on a different subnet is
 out-of-scope for this topic.
 
-// Creating a project and service  
+// Creating a project and service
 include::modules/nw-creating-project-and-service.adoc[leveloffset=+1]
 
 // Exposing the service by creating a route
@@ -48,6 +48,6 @@ include::modules/nw-exposing-service.adoc[leveloffset=+1]
 [id="configuring-ingress-cluster-traffic-nodeport-additional-resources"]
 == Additional resources
 
-* xref:../../networking/configuring-node-port-service-range.adoc#configuring-node-port-service-range[Configuring the node port service range]
+* xref:../../../networking/configuring_network_settings/configuring-node-port-service-range.adoc#configuring-node-port-service-range[Configuring the node port service range]
 
-* xref:../../networking/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc#nw-ingress-controller-nodeportservice-projects_nw-configuring-ingress-controller-endpoint-publishing-strategy[Adding a single NodePort service to an Ingress Controller]
+* xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc#nw-ingress-controller-nodeportservice-projects_nw-configuring-ingress-controller-endpoint-publishing-strategy[Adding a single NodePort service to an Ingress Controller]

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-service-external-ip.adoc

@@ -6,14 +6,14 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-You can use either a MetalLB implementation or an IP failover deployment to attach an ExternalIP resource to a service so that the service is available to traffic outside your {product-title} cluster. Hosting an external IP address in this way is only applicable for a cluster installed on bare-metal hardware. 
+You can use either a MetalLB implementation or an IP failover deployment to attach an ExternalIP resource to a service so that the service is available to traffic outside your {product-title} cluster. Hosting an external IP address in this way is only applicable for a cluster installed on bare-metal hardware.
 
 You must ensure that you correctly configure the external network infrastructure to route traffic to the service.
 
 [id="configuring-ingress-cluster-traffic-service-external-ip-prerequisites"]
 == Prerequisites
 
-* Your cluster is configured with ExternalIPs enabled. For more information, read xref:../../networking/configuring_ingress_cluster_traffic/configuring-externalip.adoc#configuring-externalip[Configuring ExternalIPs for services].
+* Your cluster is configured with ExternalIPs enabled. For more information, read xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-externalip.adoc#configuring-externalip[Configuring ExternalIPs for services].
 +
 [NOTE]
 ====
@@ -26,8 +26,8 @@ include::modules/nw-service-externalip-create.adoc[leveloffset=+1]
 [id="configuring-ingress-cluster-traffic-service-external-ip-additional-resources"]
 == Additional resources
 
-* xref:../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator]
+* xref:../../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator]
 
-* xref:../../networking/configuring-ipfailover.adoc#configuring-ipfailover[Configuring IP failover]
+* xref:../../../networking/configuring_network_settings/configuring-ipfailover.adoc#configuring-ipfailover[Configuring IP failover]
 
-* xref:../../networking/configuring_ingress_cluster_traffic/configuring-externalip.adoc#configuring-externalip[Configuring ExternalIPs for services]
+* xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-externalip.adoc#configuring-externalip[Configuring ExternalIPs for services]

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/images

@@ -0,0 +1 @@
+../../images/

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/ingress-controller-dnsmgt.adoc

@@ -36,4 +36,4 @@ include::modules/modifying-an-existing-ingress-controller.adoc[leveloffset=+1]
 [role="_additional-resources"]
 [id="configuring-ingress-controller-dns-management-additional-resources"]
 == Additional resources
-* xref:../networking/networking_operators/ingress-operator.adoc#nw-ingress-controller-configuration-parameters_configuring-ingress[Ingress Controller configuration parameters]
+* xref:../../../networking/networking_operators/ingress-operator.adoc#nw-ingress-controller-configuration-parameters_configuring-ingress[Ingress Controller configuration parameters]

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/modules

@@ -0,0 +1 @@
+../../modules/

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/nw-configuring-ingress-controller-endpoint-publishing-strategy.adoc

@@ -30,8 +30,8 @@ include::modules/nw-ingress-controller-nodeportservice-projects.adoc[leveloffset
 [role="_additional-resources"]
 == Additional resources
 
-* xref:../../networking/networking_operators/ingress-operator.adoc#nw-ingress-controller-configuration-parameters_configuring-ingress[Ingress Controller configuration parameters]
+* xref:../../../networking/networking_operators/ingress-operator.adoc#nw-ingress-controller-configuration-parameters_configuring-ingress[Ingress Controller configuration parameters]
 
-* xref:../../installing/installing_openstack/installing-openstack-installer-custom.adoc#installation-osp-setting-cloud-provider-options_installing-openstack-installer-custom[Setting {rh-openstack} Cloud Controller Manager options]
+* xref:../../../installing/installing_openstack/installing-openstack-installer-custom.adoc#installation-osp-setting-cloud-provider-options_installing-openstack-installer-custom[Setting {rh-openstack} Cloud Controller Manager options]
 
-* xref:../../installing/installing_platform_agnostic/installing-platform-agnostic.html#installation-dns-user-infra_installing-platform-agnostic[User-provisioned DNS requirements]
+* xref:../../../installing/installing_platform_agnostic/installing-platform-agnostic.adoc#installation-dns-user-infra_installing-platform-agnostic[User-provisioned DNS requirements]

networking/ingress_load_balancing/configuring_ingress_cluster_traffic/overview-traffic.adoc

@@ -22,21 +22,21 @@ with the SNI header, use an Ingress Controller.
 
 |Method |Purpose
 
-|xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc#configuring-ingress-cluster-traffic-ingress-controller[Use an Ingress Controller]
+|xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc#configuring-ingress-cluster-traffic-ingress-controller[Use an Ingress Controller]
 |Allows access to HTTP/HTTPS traffic and TLS-encrypted protocols other than HTTPS (for example, TLS with the SNI header).
 
-|xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc#configuring-ingress-cluster-traffic-load-balancer[Automatically assign an external IP using a load balancer service]
+|xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc#configuring-ingress-cluster-traffic-load-balancer[Automatically assign an external IP using a load balancer service]
 |Allows traffic to non-standard ports through an IP address assigned from a pool.
 Most cloud platforms offer a method to start a service with a load-balancer IP address.
 
-|xref:../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator]
+|xref:../../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator]
 |Allows traffic to a specific IP address or address from a pool on the machine network.
 For bare-metal installations or platforms that are like bare metal, MetalLB provides a way to start a service with a load-balancer IP address.
 
-|xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-service-external-ip.adoc#configuring-ingress-cluster-traffic-service-external-ip[Manually assign an external IP to a service]
+|xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-service-external-ip.adoc#configuring-ingress-cluster-traffic-service-external-ip[Manually assign an external IP to a service]
 |Allows traffic to non-standard ports through a specific IP address.
 
-|xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#configuring-ingress-cluster-traffic-nodeport[Configure a `NodePort`]
+|xref:../../../networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc#configuring-ingress-cluster-traffic-nodeport[Configure a `NodePort`]
 |Expose a service on all nodes in the cluster.
 |===
 

networking/ingress_load_balancing/images

@@ -0,0 +1 @@
+../../images/

networking/ingress_load_balancing/load-balancing-openstack.adoc

@@ -6,9 +6,13 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+//limitations of OSP loadbalancer
 include::modules/nw-osp-loadbalancer-limitations.adoc[leveloffset=+1]
+
 include::modules/nw-osp-loadbalancer-etp-local.adoc[leveloffset=+2]
+
 include::modules/installation-osp-api-octavia.adoc[leveloffset=+1]
+
 include::modules/installation-osp-api-scaling.adoc[leveloffset=+2]
 
 // Services for a user-managed load balancer

networking/ingress_load_balancing/metallb/_attributes

@@ -0,0 +1 @@
+../../_attributes/

networking/ingress_load_balancing/metallb/about-advertising-ipaddresspool.adoc

@@ -50,4 +50,4 @@ include::modules/nw-metallb-configure-secondary-interface.adoc[leveloffset=+1]
 [id="additional-resources_about-advertiseipaddress"]
 == Additional resources
 
-* xref:../../networking/metallb/metallb-configure-community-alias.adoc#metallb-configure-community-alias[Configuring a community alias].
+* xref:../../../networking/ingress_load_balancing/metallb/metallb-configure-community-alias.adoc#metallb-configure-community-alias[Configuring a community alias].

networking/ingress_load_balancing/metallb/metallb-configure-address-pools.adoc

@@ -8,7 +8,7 @@ toc::[]
 
 As a cluster administrator, you can add, modify, and delete address pools. The MetalLB Operator uses the address pool custom resources to set the IP addresses that MetalLB can assign to services. The namespace used in the examples assume the namespace is `metallb-system`.
 
-For more information about how to install the MetalLB Operator, see xref:../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator].
+For more information about how to install the MetalLB Operator, see xref:../../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb[About MetalLB and the MetalLB Operator].
 
 // Address pool custom resource
 include::modules/nw-metallb-addresspool-cr.adoc[leveloffset=+1]
@@ -25,8 +25,8 @@ include::modules/nw-metallb-example-addresspool.adoc[leveloffset=+1]
 [id="next-steps_{context}"]
 == Next steps
 
-* xref:../../networking/metallb/about-advertising-ipaddresspool.adoc#nw-metallb-configure-with-L2-advertisement-label_about-advertising-ip-address-pool[Configuring MetalLB with an L2 advertisement and label]
+* xref:../../../networking/ingress_load_balancing/metallb/about-advertising-ipaddresspool.adoc#nw-metallb-configure-with-L2-advertisement-label_about-advertising-ip-address-pool[Configuring MetalLB with an L2 advertisement and label]
 
-* xref:../../networking/metallb/metallb-configure-bgp-peers.adoc#metallb-configure-bgp-peers[Configuring MetalLB BGP peers]
+* xref:../../../networking/ingress_load_balancing/metallb/metallb-configure-bgp-peers.adoc#metallb-configure-bgp-peers[Configuring MetalLB BGP peers]
 
-* xref:../../networking/metallb/metallb-configure-services.adoc#metallb-configure-services[Configuring services to use MetalLB]
+* xref:../../../networking/ingress_load_balancing/metallb/metallb-configure-services.adoc#metallb-configure-services[Configuring services to use MetalLB]

networking/ingress_load_balancing/metallb/metallb-configure-bfd-profiles.adoc

@@ -18,4 +18,4 @@ include::modules/nw-metallb-configure-bfdprofle.adoc[leveloffset=+1]
 [id="next-steps_{context}"]
 == Next steps
 
-* xref:../../networking/metallb/metallb-configure-bgp-peers.adoc#metallb-configure-bgp-peers[Configure a BGP peer] to use the BFD profile.
+* xref:../../../networking/ingress_load_balancing/metallb/metallb-configure-bgp-peers.adoc#metallb-configure-bgp-peers[Configure a BGP peer] to use the BFD profile.

networking/ingress_load_balancing/metallb/metallb-configure-bgp-peers.adoc

@@ -29,13 +29,13 @@ include::modules/nw-metallb-configure-vrf-bgppeer.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/multiple_networks/about-virtual-routing-and-forwarding.adoc#cnf-about-virtual-routing-and-forwarding_about-virtual-routing-and-forwarding[About virtual routing and forwarding]
+* xref:../../../networking/multiple_networks/about-virtual-routing-and-forwarding.adoc#cnf-about-virtual-routing-and-forwarding_about-virtual-routing-and-forwarding[About virtual routing and forwarding]
 
-* xref:../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#virt-example-host-vrf_k8s-nmstate-updating-node-network-config[Example: Network interface with a VRF instance node network configuration policy]
+* xref:../../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#virt-example-host-vrf_k8s-nmstate-updating-node-network-config[Example: Network interface with a VRF instance node network configuration policy]
 
-* xref:../../networking/ovn_kubernetes_network_provider/configuring-egress-traffic-for-vrf-loadbalancer-services.adoc#configuring-egress-traffic-loadbalancer-services[Configuring an egress service]
+* xref:../../../networking/ovn_kubernetes_network_provider/configuring-egress-traffic-for-vrf-loadbalancer-services.adoc#configuring-egress-traffic-loadbalancer-services[Configuring an egress service]
 
-* xref:../../networking/metallb/metallb-configure-return-traffic.adoc#metallb-configure-return-traffic[Managing symmetric routing with MetalLB]
+* xref:../../../networking/ingress_load_balancing/metallb/metallb-configure-return-traffic.adoc#metallb-configure-return-traffic[Managing symmetric routing with MetalLB]
 
 // Examples
 include::modules/nw-metallb-example-bgppeer.adoc[leveloffset=+1]
@@ -43,4 +43,4 @@ include::modules/nw-metallb-example-bgppeer.adoc[leveloffset=+1]
 [id="next-steps_{context}"]
 == Next steps
 
-* xref:../../networking/metallb/metallb-configure-services.adoc#metallb-configure-services[Configuring services to use MetalLB]
+* xref:../../../networking/ingress_load_balancing/metallb/metallb-configure-services.adoc#metallb-configure-services[Configuring services to use MetalLB]

networking/ingress_load_balancing/metallb/metallb-configure-return-traffic.adoc

@@ -55,10 +55,10 @@ include::modules/nw-metallb-configure-return-traffic-proc.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../networking/multiple_networks/about-virtual-routing-and-forwarding.adoc#cnf-about-virtual-routing-and-forwarding_about-virtual-routing-and-forwarding[About virtual routing and forwarding]
+* xref:../../../networking/multiple_networks/about-virtual-routing-and-forwarding.adoc#cnf-about-virtual-routing-and-forwarding_about-virtual-routing-and-forwarding[About virtual routing and forwarding]
 
-* xref:../../networking/metallb/metallb-configure-bgp-peers.adoc#nw-metallb-bgp-peer-vrf_configure-metallb-bgp-peers[Exposing a service through a network VRF]
+* xref:../../../networking/ingress_load_balancing/metallb/metallb-configure-bgp-peers.adoc#nw-metallb-bgp-peer-vrf_configure-metallb-bgp-peers[Exposing a service through a network VRF]
 
-* xref:../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#virt-example-host-vrf_k8s-nmstate-updating-node-network-config[Example: Network interface with a VRF instance node network configuration policy]
+* xref:../../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#virt-example-host-vrf_k8s-nmstate-updating-node-network-config[Example: Network interface with a VRF instance node network configuration policy]
 
-* xref:../../networking/ovn_kubernetes_network_provider/configuring-egress-traffic-for-vrf-loadbalancer-services.adoc#configuring-egress-traffic-loadbalancer-services[Configuring an egress service]
+* xref:../../../networking/ovn_kubernetes_network_provider/configuring-egress-traffic-for-vrf-loadbalancer-services.adoc#configuring-egress-traffic-loadbalancer-services[Configuring an egress service]

networking/ingress_load_balancing/metallb/metallb-troubleshoot-support.adoc

@@ -26,7 +26,7 @@ include::modules/nw-metallb-metrics.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* See xref:../../observability/monitoring/accessing-metrics/accessing-metrics-as-an-administrator.adoc#querying-metrics-for-all-projects-with-mon-dashboard_accessing-metrics-as-an-administrator[Querying metrics for all projects with the monitoring dashboard] for information about using the monitoring dashboard.
+* See xref:../../../observability/monitoring/accessing-metrics/accessing-metrics-as-an-administrator.adoc#querying-metrics-for-all-projects-with-mon-dashboard_accessing-metrics-as-an-administrator[Querying metrics for all projects with the monitoring dashboard] for information about using the monitoring dashboard.
 
 // Collecting data
 include::modules/nw-metallb-collecting-data.adoc[leveloffset=+1]
@@ -34,4 +34,4 @@ include::modules/nw-metallb-collecting-data.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../support/gathering-cluster-data.adoc#gathering-cluster-data[Gathering data about your cluster]
+* xref:../../../support/gathering-cluster-data.adoc#gathering-cluster-data[Gathering data about your cluster]

networking/ingress_load_balancing/modules

@@ -0,0 +1 @@
+../../modules/