Merge pull request #105590 from dfitzmau/OCPBUGS-73774

OCPBUGS-73774: Moved Allocating Load Balancers to Specific Subnets cl…

Author: dfitzmau

_topic_maps/_topic_map.yml

@@ -1788,8 +1788,6 @@ Topics:
       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

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

@@ -58,6 +58,15 @@ include::modules/installation-configure-proxy.adoc[leveloffset=+2]
 
 include::modules/installation-applying-aws-security-groups.adoc[leveloffset=+2]
 
+// Allocating Load Balancers to Specific Subnets
+include::modules/allocating-load-balancers.adoc[leveloffset=+2]
+
+// Allocating API and Ingress Load Balancers to Specific Subnets on AWS
+include::modules/nw-allocating-load-balancers-to-subnets.adoc[leveloffset=+3]
+
+// Specifying AWS Subnets for OpenShift Ingress Load Balancers at Installation
+include::modules/nw-allocate-load-balancers-to-subnets-procedure.adoc[leveloffset=+3]
+
 [id="installing-aws-manual-modes_{context}"]
 == Alternatives to storing administrator-level secrets in the kube-system project
 

modules/allocating-load-balancers.adoc

@@ -0,0 +1,9 @@
+:_mod-docs-content-type: CONCEPT
+[id="allocating-load-balancers_{context}"]
+= Allocating load balancers to specific subnets
+
+[role="_abstract"]
+You can manage application traffic efficiently by allocating load balancers. Network administrators can allocate load balancers to customize deployments which can ensure optimal traffic distribution, high availability of applications, uninterrupted service, and network segmentation.
+
+You can also limit subnet selection for a load balancer by using subnet roles. Subnet roles prevent security risks by ensuring Load Balancers are automatically placed only in subnets explicitly designated for public or private traffic. This eliminates manual configuration errors and guarantees architectural compliance across multiple availability zones.
+

modules/nw-allocating-load-balancers-to-subnets.adoc

@@ -4,9 +4,9 @@
 
 :_mod-docs-content-type: CONCEPT
 [id="nw-allocating-load-balancers-to-subnets_{context}"]
-= Allocating API and Ingress Load Balancers to Specific Subnets on AWS
+= Allocating API and Ingress load balancers to specific subnets on AWS
 
 [role="_abstract"]
-You can control the network placement of {product-title} Load Balancers on {aws-short}, including Load Balancers for the Ingress Controller, by explicitly defining your subnets from the virtual private cloud (VPC). You can then assign the subnets specific roles directly within the `platform.aws.vpc.subnets` section of the `install-config.yaml` file. 
+You can control the network placement of {product-title} load balancers on {aws-short}, including load balancers for the Ingress Controller, by explicitly defining your subnets from the virtual private cloud (VPC). You can then assign the subnets specific roles directly within the `platform.aws.vpc.subnets` section of the `install-config.yaml` file. 
 
 By using this method, you have granular control of subnets that are used for resources, such as the Ingress Controller and other cluster components.