Skip to content

OCPBUGS-54731: Distinguished among IPI and UPI in nw-dual-stack-conve… #91857

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −7
Open

OCPBUGS-54731: Distinguished among IPI and UPI in nw-dual-stack-conve… #91857

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions modules/nw-dual-stack-convert.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,14 +9,14 @@ As a cluster administrator, you can convert your single-stack cluster network to
After converting your cluster to use dual-stack networking, you must re-create any existing pods for them to receive IPv6 addresses, because only new pods are assigned IPv6 addresses.
====

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. You can convert to a dual-stack cluster network for a cluster that runs on installer-provisioned infrastructure.
Converting a single-stack cluster network to a dual-stack cluster network consists of creating patches and applying them to the network and infrastructure of the cluster. You can convert to a dual-stack cluster network for a cluster that runs on either installer-provisioned infrastructure or user-provisioned infrastructure.

[NOTE]
====
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.
====

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.
On installer-provisioned infrastructure only, 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 infrastructure and not the network for the cluster.

[IMPORTANT]
====
Expand Down Expand Up @@ -74,7 +74,9 @@ $ oc patch network.config.openshift.io cluster \// <1>
network.config.openshift.io/cluster patched
----

. Specify IPv6 VIPs for API and Ingress services for your cluster. Create a YAML configuration patch file that has a similar configuration to the following example:
. On installer-provisioned infrastructure where you added IPv6 VIPs for API and Ingress services, complete the following steps:
+
.. Specify IPv6 VIPs for API and Ingress services for your cluster. Create a YAML configuration patch file that has a similar configuration to the following example:
+
[source,yaml]
----
Expand All @@ -88,13 +90,14 @@ network.config.openshift.io/cluster patched
path: /spec/platformSpec/baremetal/ingressIPs/-
value: fd2e:6f44:5dd8::5
----
--
<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.
<2> Ensure that you specify each file path according to your platform. The example demonstrates a file path on a bare-metal platform.


. Patch the infrastructure by entering the following command in your CLI:
--
+
[source,terminal,subs="+quotes,"]
.. Patch the infrastructure by entering the following command in your CLI:
+
[source,terminal,subs="+quotes"]
----
$ oc patch infrastructure cluster \// <1>
--type='json' --patch-file <file>.yaml
Expand Down