Skip to content

Commit 972a7a3

Browse files
mletaliemletalie
committed
sdnovnosd
1 parent da3def6 commit 972a7a3

File tree

5 files changed

+151
-2
lines changed

5 files changed

+151
-2
lines changed

‎_topic_maps/_topic_map_osd.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -868,6 +868,8 @@ Topics:
868868
Topics:
869869
- Name: About the OVN-Kubernetes network plugin
870870
File: about-ovn-kubernetes
871+
- Name: Migrating from the OpenShift SDN network plugin
872+
File: migrate-from-openshift-sdn-osd
871873
- Name: OpenShift SDN network plugin
872874
Dir: ovn_kubernetes_network_provider
873875
Topics:

‎modules/migrate-sdn-ovn-osd.adoc

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
// Module included in the following assemblies:
2+
//networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc
3+
4+
:_mod-docs-content-type: PROCEDURE
5+
[id="migrate-sdn-ovn-ocm-cli_{context}"]
6+
= Initiate migration using the OpenShift Cluster Manager API command-line interface (ocm) CLI
7+
8+
[WARNING]
9+
====
10+
You can only initiate migration on clusters that are version 4.16.24 and above.
11+
====
12+
13+
.Prerequisites
14+
15+
* You installed the link:https://console.redhat.com/openshift/downloads[OpenShift Cluster Manager API command-line interface (`ocm`)].
16+
17+
[IMPORTANT]
18+
====
19+
[subs="attributes+"]
20+
OpenShift Cluster Manager API command-line interface (`ocm`) is a Technology Preview feature only.
21+
For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
22+
====
23+
24+
.Procedure
25+
26+
. Create a JSON file with the following content:
27+
28+
+
29+
[source,json]
30+
----
31+
{
32+
"type": "sdnToOvn"
33+
}
34+
----
35+
+
36+
37+
** Optional: Within the JSON file, you can configure internal subnets using any or all of the options `join`, `masquerade`, and `transit`, along with a single CIDR per option, as shown in the following example:
38+
+
39+
[source,json]
40+
----
41+
{
42+
"type": "sdnToOvn",
43+
"sdn_to_ovn": {
44+
"transit_ipv4": "192.168.255.0/24",
45+
"join_ipv4": "192.168.255.0/24",
46+
"masquerade_ipv4": "192.168.255.0/24"
47+
}
48+
}
49+
----
50+
+
51+
[NOTE]
52+
====
53+
OVN-Kubernetes reserves the following IP address ranges:
54+
55+
`100.64.0.0/16`. This IP address range is used for the `internalJoinSubnet` parameter of OVN-Kubernetes by default.
56+
57+
`100.88.0.0/16`. This IP address range is used for the `internalTransSwitchSubnet` parameter of OVN-Kubernetes by default.
58+
59+
If these IP addresses have been used by OpenShift SDN or any external networks that might communicate with this cluster, you must patch them to use a different IP address range before initiating the limited live migration. For more information, see _Patching OVN-Kubernetes address ranges_ in the _Additional resources_ section.
60+
====
61+
+
62+
63+
. To initiate the migration, run the following post request in a terminal window:
64+
65+
+
66+
[source,terminal]
67+
----
68+
$ ocm post /api/clusters_mgmt/v1/clusters/{cluster_id}/migrations <1>
69+
--body=myjsonfile.json <2>
70+
----
71+
<1> Replace `{cluster_id}` with the ID of the cluster you want to migrate to the OVN-Kubernetes network plugin.
72+
<2> Replace `myjsonfile.json` with the name of the JSON file you created in the previous step.
73+
+
74+
.Example output
75+
+
76+
[source,json]
77+
----
78+
{
79+
"kind": "ClusterMigration",
80+
"href": "/api/clusters_mgmt/v1/clusters/2gnts65ra30sclb114p8qdc26g5c8o3e/migrations/2gois8j244rs0qrfu9ti2o790jssgh9i",
81+
"id": "7sois8j244rs0qrhu9ti2o790jssgh9i",
82+
"cluster_id": "2gnts65ra30sclb114p8qdc26g5c8o3e",
83+
"type": "sdnToOvn",
84+
"state": {
85+
"value": "scheduled",
86+
"description": ""
87+
},
88+
"sdn_to_ovn": {
89+
"transit_ipv4": "100.65.0.0/16",
90+
"join_ipv4": "100.66.0.0/16"
91+
},
92+
"creation_timestamp": "2025-02-05T14:56:34.878467542Z",
93+
"updated_timestamp": "2025-02-05T14:56:34.878467542Z"
94+
}
95+
----
96+
97+
// :_mod-docs-content-type: PROCEDURE
98+
// [id="verify-sdn-ovn-ocm_{context}"]
99+
// = Verify migration status using the OCM CLI
100+
101+
.Verification
102+
103+
* To check the status of the migration, run the following command:
104+
105+
+
106+
107+
[source,terminal]
108+
----
109+
$ ocm get cluster $cluster_id/migration <1>
110+
----
111+
<1> Replace `$cluster_id` with the ID of the cluster that the migration was applied to.

‎networking/about-managed-networking.adoc

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,12 +19,16 @@ The following are some of the most commonly used {openshift-networking} features
1919
+
2020
[IMPORTANT]
2121
====
22-
You cannot migrate an {OCP-short} 4.16 cluster that uses the SDN network plugin to {OCP-short} 4.17 because no migration path currently exists.
22+
Before upgrading {product-title} clusters that are configured with the OpenShift SDN network plugin to version 4.17, you must migrate to the OVN-Kubernetes network plugin. For more information, see _Migrating from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin_ in the _Additional resources_ section.
2323
====
2424
2525
[discrete]
2626
[role="_additional-resources"]
2727
[id="additional-resources_{context}"]
2828
== Additional resources
2929

30-
* link:https://access.redhat.com/articles/7065170[{OCP-short} SDN CNI removal in OCP 4.17]
30+
* link:https://access.redhat.com/articles/7065170[{OCP-short} SDN CNI removal in OCP 4.17]
31+
32+
ifdef::openshift-dedicated[]
33+
* xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn-osd.adoc#migrate-from-openshift-sdn-osd[Migrating from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin]
34+
endif::openshift-dedicated[]

‎networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn-osd.adoc

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="migrate-from-openshift-sdn-osd"]
3+
= Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin
4+
include::_attributes/common-attributes.adoc[]
5+
include::_attributes/attributes-openshift-dedicated.adoc[]
6+
:context: migrate-from-openshift-sdn
7+
8+
toc::[]
9+
10+
As an {product-title} cluster administrator, you can initiate the migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin and verify the migration status using the OCM CLI.
11+
12+
Some considerations before starting migration initiation are:
13+
14+
* The cluster version must be 4.16.24 and above.
15+
* The migration process cannot be interrupted.
16+
* Migrating back to the SDN network plugin is not possible.
17+
* Cluster nodes will be rebooted during migration.
18+
* There will be no impact to workloads that are resilient to node disruptions.
19+
* Migration time can vary between several minutes and hours, depending on the cluster size and workload configurations.
20+
21+
include::modules/migrate-sdn-ovn-osd.adoc[leveloffset=+1]
22+
23+
.Additional resources
24+
link:https://docs.openshift.com/container-platform/4.16/networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.html#patching-ovnk-address-ranges_migrate-from-openshift-sdn[Patching OVN-Kubernetes address ranges]

‎osd_whats_new/osd-whats-new.adoc

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,14 @@ With its foundation in Kubernetes, {product-title} is a complete {OCP} cluster p
1919
=== Q1 2025
2020

2121
* **Cluster node limit update.** {product-title} clusters versions 4.14.14 and greater can now scale to 249 worker nodes. This is an increase from the previous limit of 180 nodes. For more information, see xref:../osd_planning/osd-limits-scalability.adoc#osd-limits-scalability[limits and scalability].
22+
// * **{product-title} SDN network plugin blocks future major upgrades**
23+
* **Initiate live migration from OpenShift SDN to OVN-Kubernetes.**
24+
As part of the {product-title} move to OVN-Kubernetes as the only supported network plugin starting with {product-title} version 4.17, users can now initiate live migration from the OpenShift SDN network plugin to the OVN-Kubernetes network plugin.
25+
+
26+
If your cluster uses the OpenShift SDN network plugin, you cannot upgrade to future major versions of {product-title} without migrating to OVN-Kubernetes.
27+
+
28+
For more information about migrating to OVN-Kubernetes, see xref:../networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn-osd.adoc#migrate-from-openshift-sdn[Migrating from OpenShift SDN network plugin to OVN-Kubernetes network plugin].
29+
2230

2331
* **Red{nbsp}Hat SRE log-based alerting endpoints have been updated.** {product-title} customers who are using a firewall to control egress traffic can now remove all references to `*.osdsecuritylogs.splunkcloud.com:9997` from your firewall allowlist. {product-title} clusters still require the `http-inputs-osdsecuritylogs.splunkcloud.com:443` log-based alerting endpoint to be accessible from the cluster.
2432

0 commit comments

Comments
 (0)