Skip to content

Commit 9ca4062

Browse files
authored
Merge pull request #87834 from dfitzmau/OCPBUGS-39568-fix
OCPBUGS-39568-fix: Added note about 3rd party plugin to OVNK plugin]
2 parents ea31514 + f5cff6f commit 9ca4062

File tree

1 file changed

+17
-10
lines changed

1 file changed

+17
-10
lines changed

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

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,26 +6,33 @@ include::_attributes/common-attributes.adoc[]
66
// Unique attribute for the version of the release notes.
77

88
toc::[]
9+
10+
As a cluster administrator, you can migrate to the OVN-Kubernetes network plugin from the OpenShift software-defined networking (SDN) plugin.
911

10-
As a cluster administrator, you can migrate to the OVN-Kubernetes network plugin from the OpenShift SDN network plugin. The following options are available for migration:
12+
[WARNING]
13+
====
14+
If your cluster uses the OpenShift SDN network plugin, you cannot upgrade your cluster to {product-title} 4.17. You must initially migrate your cluster to the OVN-Kubernetes plugin and then upgrade your cluster to {product-title} 4.17.
15+
16+
Additionally, if your cluster uses a third-party container network interface (CNI) plugin, you cannot migrate your cluster to the OVN-Kubernetes network plugin. For a complete list of these CNI plugins, see link:https://access.redhat.com/articles/5436171[Certified OpenShift CNI Plug-ins] (Red{nbsp}Hat Knowledgebase).
17+
====
18+
19+
The following methods exist for migrating from the OpenShift SDN network plugin to the OVN-Kubernetes plugin:
1120

1221
Limited live migration (preferred method)::
13-
This is an automated process that migrates your cluster from OpenShift SDN to OVN-Kubernetes without service interruption.
22+
This is an automated process that migrates your cluster from OpenShift SDN to OVN-Kubernetes.
1423

1524
Offline migration::
16-
This is a manual process that includes some downtime. This method is primarily used for self-managed {product-title} deployments, and should be used in the event that you cannot perform a limited live migration to the OVN-Kubernetes network plugin.
25+
This is a manual process that includes some downtime. This method is primarily used for self-managed {product-title} deployments, and consider using this method when you cannot perform a limited live migration to the OVN-Kubernetes network plugin.
1726

1827
[WARNING]
19-
====
20-
It is not possible to upgrade a cluster to {product-title} 4.17 if it is using the OpenShift SDN network plugin. You must migrate to the OVN-Kubernetes plugin before upgrading to {product-title} 4.17.
28+
====
29+
For the limited live migration method only, do not automate the migration from OpenShift SDN to OVN-Kubernetes with a script or another tool such as Red{nbsp}Hat Ansible Automation Platform. This might cause outages or crash your {product-title} cluster.
2130
====
2231

23-
To learn more about OVN-Kubernetes, read xref:../../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes#about-ovn-kubernetes[About the OVN-Kubernetes network plugin].
32+
[role="_additional-resources"]
33+
.Additional resources
2434

25-
[WARNING]
26-
====
27-
Do not automate the migration from OpenShift SDN to OVN-Kubernetes with a script or another tool like Red Hat Ansible Automation Platform. This might cause outages or crash your {product-title} cluster.
28-
====
35+
* xref:../../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes#about-ovn-kubernetes[About the OVN-Kubernetes network plugin]
2936
3037
// Offline migration to the OVN-Kubernetes network plugin overview
3138
include::modules/nw-ovn-kubernetes-migration-about.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)