Skip to content

Commit 25c17f5

Browse files
authored
Merge pull request #76001 from dfitzmau/OSDOCS-10539
OSDOCS-10539: Added note about upgrading existing dual-stack net to 4.16
2 parents c9fecc4 + ec51638 commit 25c17f5

File tree

1 file changed

+18
-3
lines changed

1 file changed

+18
-3
lines changed

modules/nw-dual-stack-convert.adoc

Lines changed: 18 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,28 @@ As a cluster administrator, you can convert your single-stack cluster network to
66

77
Converting a single-stack cluster network to a dual-stack cluster network consists of creating patches and applying them to the cluster's network and infrastructure.
88

9-
If you need to add IPv6 Virtual IPs (VIPs) for API and Ingress services to an existing dual-stack-configured cluster, you need to patch only the cluster's infrastructure and not the cluster's network.
10-
119
[NOTE]
1210
====
1311
Each patch operation that changes `clusterNetwork`, `serviceNetwork`, `apiServerInternalIPs`, and `ingressIP` objects triggers a restart of the cluster. Changing the `MachineNetworks` object does not cause a reboot of the cluster.
1412
====
1513

14+
If you need to add IPv6 virtual IPs (VIPs) for API and Ingress services to an existing dual-stack-configured cluster, you need to patch only the cluster's infrastructure and not the cluster's network.
15+
16+
[IMPORTANT]
17+
====
18+
If you already upgraded your cluster to {product-title} 4.16 or later and you need to convert the single-stack cluster network to a dual-stack cluster network, you must specify an existing IPv4 `machineNetwork` network configuration from the `install-config.yaml` file for API and Ingress services in the YAML configuration patch file. This configuration ensures that IPv4 traffic exists in the same network interface as the default gateway.
19+
20+
.Example YAML configuration file with an added IPv4 address block for the `machineNetwork` network
21+
[source,yaml]
22+
----
23+
- op: add
24+
path: /spec/platformSpec/baremetal/machineNetworks/- <1>
25+
value: 192.168.1.0/24
26+
# ...
27+
----
28+
<1> Ensure that you specify an address block for the `machineNetwork` network where your machines operate. You must select both API and Ingress IP addresses for the machine network.
29+
====
30+
1631
.Prerequisites
1732

1833
* You installed the OpenShift CLI (`oc`).
@@ -23,7 +38,7 @@ Each patch operation that changes `clusterNetwork`, `serviceNetwork`, `apiServer
2338
2439
.Procedure
2540

26-
. To specify IPv6 address blocks for the cluster and service networks, create a YAML configuration patch file that has a similar configuration to the following example:
41+
. To specify IPv6 address blocks for cluster and service networks, create a YAML configuration patch file that has a similar configuration to the following example:
2742
+
2843
[source,yaml]
2944
----

0 commit comments

Comments
 (0)