Merge pull request #87989 from jldohmann/OSDOCS-9474

OSDOCS-9474: add aws eip procedure

Author: jldohmann

modules/nw-ingress-aws-static-eip-nlb-configuration.adoc

@@ -0,0 +1,74 @@
+// Modules included in the following assemblies:
+//
+// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="nw-ingress-aws-static-eip-nlb-configuration_{context}"]
+= Configuring AWS Elastic IP (EIP) addresses for a Network Load Balancer (NLB)
+
+You can specify static IPs, otherwise known as elastic IPs, for your network load balancer (NLB) in the Ingress Controller. This is useful in situations where you want to configure appropriate firewall rules for your cluster network.
+
+.Prerequisites
+* You must have an installed AWS cluster.
+* You must know the names or IDs of the subnets to which you intend to map your `IngressController`.
+
+.Procedure
+
+. Create a YAML file that contains the following content:
++
+.`sample-ingress.yaml`
+[source,yaml]
+----
+apiVersion: operator.openshift.io/v1
+kind: IngressController
+metadata:
+  namespace: openshift-ingress-operator
+  name: <name> <1>
+spec:
+  domain: <domain> <2>
+  endpointPublishingStrategy:
+    loadBalancer:
+      scope: External <3>
+      type: LoadBalancerService
+      providerParameters:
+        type: AWS
+        aws:
+          type: NLB
+          networkLoadBalancer:
+            subnets: <4>
+              ids:
+              - <subnet_ID>
+              names:
+              - <subnet_A>
+              - <subnet_B>
+            eipAllocations: <5>
+            - <eipalloc_A>
+            - <eipalloc_B>
+            - <eipalloc_C>
+----
+<1> Replace the `<name>` placeholder with a name for the Ingress Controller.
+<2> Replace the `<domain>` placeholder with the DNS name serviced by the Ingress Controller.
+<3> The scope must be set to the value `External` and be Internet-facing in order to allocate EIPs.
+<4> Specify the IDs and names for your subnets. The total number of IDs and names must be equal to your allocated EIPs.
+<5> Specify the EIP addresses.
++
+[IMPORTANT]
+====
+You can specify a maximum of one subnet per availability zone. Only provide public subnets for external Ingress Controllers. You can associate one EIP address per subnet.
+====
+
+. Save and apply the CR file by entering the following command:
++
+[source,terminal]
+----
+$  oc apply -f sample-ingress.yaml
+----
+
+.Verification
+
+. Confirm the load balancer was provisioned successfully by checking the `IngressController` conditions by running the following command:
++
+[source,terminal]
+----
+$ oc get ingresscontroller -n openshift-ingress-operator <name> -o jsonpath="{.status.conditions}" | yq -PC
+----

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

@@ -44,6 +44,8 @@ include::modules/nw-ingress-setting-select-subnet-loadbalancerservice.adoc[level
 
 include::modules/nw-ingress-setting-update-subnet-loadbalancerservice.adoc[leveloffset=+2]
 
+include::modules/nw-ingress-aws-static-eip-nlb-configuration.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 [id="additional-resources_configuring-ingress-cluster-traffic-aws"]
 == Additional resources