Skip to content

Commit b8e32a3

Browse files
committed
OSDOCS-54869:fixes correct YAML nesting for UDN and CUDN configs table
1 parent 1f81a03 commit b8e32a3

File tree

1 file changed

+18
-12
lines changed

1 file changed

+18
-12
lines changed

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

Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,37 +8,43 @@
88

99
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.
1010

11-
.`UserDefinedNetworks` optional configurations
12-
[cols="1,1,7", options="header"]
11+
. Optional configurations for user-defined networks
12+
[cols="2,1,7", options="header"]
1313
|====
1414

15-
|Field|Type|Description
15+
|CUDN field|UDN field|Type|Description
1616

17-
|`spec.joinSubnets`
17+
|`spec.network.<topology>.joinSubnets`
18+
|`spec.<topology>.joinSubnets`
1819
|object
1920
|When omitted, the platform sets default values for the `joinSubnets` field of `100.65.0.0/16` for IPv4 and `fd99::/64` for IPv6. If the default address values are used anywhere in the cluster's network you must override it by setting the `joinSubnets` field. If you choose to set this field, ensure it does not conflict with other subnets in the cluster such as the cluster subnet, the `default` network cluster subnet, and the masquerade subnet.
2021

2122
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.
2223

23-
|`spec.ipam.lifecycle`
24+
|`spec.network.<topology>.ipam.lifecycle`
25+
|`spec.<topology>.ipam.lifecycle`
2426
|object
25-
|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
26-
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.
27+
|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.
2728

28-
Setting a value of `Persistent` is only supported when `spec.ipam.mode` is set to `Enabled`.
29+
Setting a value of Persistent is only supported when `ipam.mode` parameter is set to `Enabled`.
2930

30-
|`spec.ipam.mode`
31+
|`spec.network.<topology>.ipam.mode`
32+
|`spec.network.<topology>.ipam.mode`
3133
|object
32-
|The `spec.ipam.mode` field controls how much of the IP configuration is managed by OVN-Kubernetes. The following options are available:
34+
|The `mode` parameter controls how much of the IP configuration is managed by OVN-Kubernetes. The following options are available:
3335

3436
**Enabled:** +
3537
When enabled, OVN-Kubernetes applies the IP configuration to the SDN infrastructure and assigns IP addresses from the selected subnet to the individual pods. This is the default setting. When set to `Enabled`, the `subnets` field must be defined. `Enabled` is the default configuration.
3638

3739
**Disabled:** +
3840
When disabled, OVN-Kubernetes only assigns MAC addresses and provides layer 2 communication, which allows users to configure IP addresses. `Disabled` is only available for layer 2 (secondary) networks. By disabling IPAM, features that rely on selecting pods by IP, for example, network policy, services, and so on, no longer function. Additionally, IP port security is also disabled for interfaces attached to this network. The `subnets` field must be empty when `spec.ipam.mode` is set to `Disabled.`
3941

40-
|`spec.layer2.mtu` and `spec.layer3.mtu`
42+
|`spec.network.<topology>.mtu`
43+
|`spec.<topology>.mtu`
4144
|integer
4245
|The maximum transmission units (MTU). The default value is `1400`. The boundary for IPv4 is `576`, and for IPv6 it is `1280`.
46+
|====
47+
48+
where:
4349

44-
|====
50+
`<topology>`:: Is one of `layer2` or `layer3`.

0 commit comments

Comments
 (0)