Skip to content

Commit 9bb002e

Browse files
author
mikemckiernan
authored
Merge pull request #33836 from mikemckiernan/feat-egress-router-cr
Restore SDN to OVN migration intro
2 parents bc3e8bf + 6a97abc commit 9bb002e

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

modules/nw-ovn-kubernetes-migration-about.adoc

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,21 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * networking/ovn_kubernetes_network_provider/migrate-from-openshift-sdn.adoc
4+
5+
[id="nw-ovn-kubernetes-migration-about_{context}"]
6+
= Migration to the OVN-Kubernetes network provider
7+
8+
Migrating to the OVN-Kubernetes Container Network Interface (CNI) cluster network provider is a manual process that includes some downtime during which your cluster is unreachable. Although a rollback procedure is provided, the migration is intended to be a one-way process.
9+
10+
[id="considerations-migrating-ovn-kubernetes-network-provider_{context}"]
11+
== Considerations for migrating to the OVN-Kubernetes network provider
12+
13+
The subnets assigned to nodes and the IP addresses assigned to individual pods are not preserved during the migration.
14+
15+
While the OVN-Kubernetes network provider implements many of the capabilities present in the OpenShift SDN network provider, the configuration is not the same.
16+
17+
* If your cluster uses any of the following OpenShift SDN capabilities, you must manually configure the same capability in OVN-Kubernetes:
18+
+
119
--
220
* Namespace isolation
321
* Egress IP addresses

0 commit comments

Comments
 (0)