Skip to content

Commit 7971128

Browse files
authored
Merge pull request #88231 from stevsmit/exiting-rules-udn
Updates additional configuration rules for UDN
2 parents 8d9827a + 76e8978 commit 7971128

File tree

1 file changed

+16
-3
lines changed

1 file changed

+16
-3
lines changed

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

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,12 +20,25 @@ The following table explains additional configurations for UDN that are optional
2020

2121
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.
2222

23-
|`spec.IPAMLifecycle`
23+
|`spec.ipam.lifecycle`
2424
|object
25-
|The `IPAMLifecycle` field configures the IP address management system (IPAM). You might use this field for virtual workloads to ensure persistent IP addresses. This field is allowed when `topology` is `layer2`. The `subnets` field must be specified when this field is specified. Setting a value of `Persistent` 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.
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+
28+
Setting a value of `Persistent` is only supported when `spec.ipam.mode` is set to `Enabled`.
29+
30+
|`spec.ipam.mode`
31+
|object
32+
|The `spec.ipam.mode` field controls how much of the IP configuration is managed by OVN-Kubernetes. The following options are available:
33+
34+
**Enabled:** +
35+
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.
36+
37+
**Disabled:** +
38+
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.`
2639

2740
|`spec.layer2.mtu` and `spec.layer3.mtu`
2841
|integer
29-
|The maximum transmission units (MTU). The default value is `1400`. The boundary for IPv4 is `574`, and for IPv6 it is `1280`.
42+
|The maximum transmission units (MTU). The default value is `1400`. The boundary for IPv4 is `576`, and for IPv6 it is `1280`.
3043

3144
|====

0 commit comments

Comments
 (0)