OSDOCS-15266:updates additional configs for UDN ingress/egress non-nated

updates from QE

Author: JoeAldinger

modules/nw-udn-additional-config-details.adoc

@@ -9,7 +9,7 @@
 The following table explains additional configurations for `ClusterUserDefinedNetwork` and `UserDefinedNetwork` custom resources (CRs) that are optional. It is not recommended to set these fields without explicit need and understanding of OVN-Kubernetes network topology.
 
 . Optional configurations for user-defined networks
-[cols="2,1,7", options="header"]
+[cols="2,1,7",options="header"]
 |====
 
 |CUDN field|UDN field|Type|Description
@@ -22,14 +22,30 @@ The following table explains additional configurations for `ClusterUserDefinedNe
 The `joinSubnets` field configures the routing between different segments within a user-defined network. Dual-stack clusters can set 2 subnets, one for each IP family; otherwise, only 1 subnet is allowed. This field is only allowed for the `Primary` network.
 
 |`spec.network.<topology>.excludeSubnets`
-|`spec.<topology>.exlcudeSubnets`
+|`spec.<topology>.excludeSubnets`
 |string
-|Specifies a list of CIDRs to be removed from the specified CIDRs in the `subnets` field. The CIDRs in this list must be in range of at least one subnet specified in `subnets`. When omitted, no IP addresses are excluded, and all IP addresses specified in the `subnets` field are subject to assignment. You must use standard CIDR notation. For example, `10.128.0.0/16`. This field must be omitted if the `subnets` field is not set or if the `ipam.mode` field is set to `Disabled`. You can only set 25 values for the `excludeSubnets` field.
+|Specifies a list of CIDRs to be removed from the CIDRs specified in the `subnets` field. The CIDRs in this list must be in range of at least one subnet specified in the `subnets` field. When omitted, OVN-Kubernetes assigns all IP addresses specified in the `subnets` field. You must use standard CIDR notation. For example, `10.128.0.0/16`. You must omit this field if the `subnets` field is not set or if the `ipam.mode` field is set to `Disabled`. You can only set 25 values for the `excludeSubnets` field.
 
 When deploying a secondary network with `Localnet` topology, the IP ranges used in your physical network must be explicitly listed in the `excludeSubnets` field to prevent IP duplication in your subnet.
 
+|`spec.network.layer2.reservedSubnets`
+|`spec.layer2.reservedSubnets`
+|object
+|This optional field specifies a list of CIDRs reserved for static IP assignment, which therefore excludes it from automatic allocation.
+When omitted, all IP addresses in the `subnets` field are available for automatic assignment. All IP addresses in the listed ranges are available to request through static IP assignment in pod annotations. Each address must be in the CIDR range specified in the `subnets` field. The field only accepts 25 entries. The format should match standard CIDR notation (for example, `10.128.0.0/16`). You must omit this field if the `subnets` field is unset or the `ipam.mode` field is `Disabled`. Specifies a reserved list of addresses for workloads. You can set this field to reserve IP addresses that pods can then request in the future.
+
+|`spec.network.layer2.infrastructureSubnets`
+|`spec.layer2.infrastructureSubnets`
+|object
+|This optional field specifies addresses used for OVN-Kubernetes internal network infrastructure. You cannot assign any IP addresses within these ranges to workloads. When omitted, OVN-Kubernetes automatically assigns IP addresses from the `subnets` field for its infrastructure needs. When the `reservedSubnets` field are also specified, the CIDRs cannot overlap. Additionally when the `defaultGatewayIPs` field are also specified, the default gateway IP addresses must belong to one of the CIDRs. Each address must be in the CIDR range specified in `subnets`. The maximum number of entries allowed is 10. The format should match standard CIDR notation (for example, `10.128.0.0/16`). You must omit this field if the `subnets` field is unset or the `ipam.mode` field is `Disabled`.
+
+|`spec.network.layer2.defaultGatewayIPs`
+|`spec.layer2.defaultGatewayIPs`
+|object
+|This field is optional and specifies an IP address that overrides the addresses assigned by default for the gateway. Acceptable values are both IPv4 and IPv6 addresses for dual stack clusters. Specifies the default gateway IP address used in the internal OVN-Kubernetes topology. Dual-stack clusters can set two IP addresses (one for each IP family), otherwise only one IP address can be used. This field is only allowed when the `role` field is set to `Primary`. It is not recommended to set this field without explicit need and understanding of the OVN-Kubernetes network topology. When omitted, OVN-Kubernetes assigns the first IP address from the network's `subnet` field.
+
 |`spec.network.<topology>.ipam.lifecycle`
-|`spec.<topology>.ipam.lifecycle`
+|`spec.layer2.ipam.lifecycle`
 |object
 |The `spec.ipam.lifecycle` field configures the IP address management system (IPAM). You might use this field for virtual workloads to ensure persistent IP addresses. The only allowed value is `Persistent`, which ensures that your virtual workloads have persistent IP addresses across reboots and migration. These are assigned by the container network interface (CNI) and used by OVN-Kubernetes to program pod IP addresses. You must not change this for pod annotations.