Ingress and load balancing

Author: JoeAldinger

_topic_maps/_topic_map.yml

@@ -1552,9 +1552,72 @@ 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
+- Name: Ingress and load balancing
+  Dir: ingress_load_balancing
   Distros: openshift-enterprise,openshift-origin
+  Topics:
+  - 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: Verifying connectivity to an endpoint
   File: verifying-connectivity-endpoint
 - Name: Changing the cluster network MTU
@@ -1686,51 +1749,6 @@ Topics:
     File: tracking-network-flows
   - Name: Configuring hybrid networking
     File: configuring-hybrid-networking
-- Name: Configuring Routes
-  Dir: routes
-  Topics:
-  - Name: Route configuration
-    File: route-configuration
-  - Name: Secured routes
-    File: secured-routes
-- Name: Configuring ingress cluster traffic
-  Dir: configuring_ingress_cluster_traffic
-  Topics:
-  - Name: Overview
-    File: overview-traffic
-    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)
 - Name: Kubernetes NMState
   Dir: k8s_nmstate
@@ -1745,29 +1763,6 @@ Topics:
 - 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
 ---

_topic_maps/_topic_map_osd.yml

@@ -787,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

@@ -984,6 +984,7 @@ Distros: openshift-rosa
 Topics:
 - Name: Networking overview
   Dir: networking_overview
+  Distros: openshift-rosa
   Topics:
   - Name: About networking
     File: about-managed-networking
@@ -1053,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

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::[]

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.

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,20 +122,20 @@ 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
 An image stream stores a mapping of tags to images, metadata overrides that are applied when images are tagged in a stream, and an optional reference to a Docker image repository on a registry.
 
 [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.
 

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

@@ -65,7 +65,7 @@ include::modules/edge-machine-pools-aws-local-zones.adoc[leveloffset=+2]
 * xref:../../../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]