Skip to content

Commit d3b9ee2

Browse files
authored
Merge pull request #75869 from dfitzmau/OSDOCS-9277-new
OSDOCS-9277-new:State NMState wait-ip parameter in dual-stack network…
2 parents ddc62f3 + f7a2777 commit d3b9ee2

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

modules/ipi-install-modifying-install-config-for-dual-stack-network.adoc

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,23 @@ serviceNetwork:
2828
- fd03::/112
2929
----
3030

31+
[IMPORTANT]
32+
====
33+
If you specified an NMState configuration in the `networkConfig` section of your `install-config.yaml` file, ensure you add `interfaces.wait-ip: ipv4+ipv6` to the NMState YAML file to resolve an issue that prevents your cluster from deploying on a dual-stack network.
34+
35+
.Example NMState YAML configuration file that includes the `wait-ip` parameter
36+
[source,yaml]
37+
----
38+
networkConfig:
39+
nmstate:
40+
interfaces:
41+
- name: <interface_name>
42+
# ...
43+
wait-ip: ipv4+ipv6
44+
# ...
45+
----
46+
====
47+
3148
To provide an interface to the cluster for applications that use IPv4 and IPv6 addresses, configure IPv4 and IPv6 virtual IP (VIP) address endpoints for the Ingress VIP and API VIP services. To configure IPv4 and IPv6 address endpoints, edit the `apiVIPs` and `ingressVIPs` configuration settings in the `install-config.yaml` file . The `apiVIPs` and `ingressVIPs` configuration settings use a list format. The order of the list indicates the primary and secondary VIP address for each service.
3249

3350
ifdef::vsphere[]

0 commit comments

Comments
 (0)