OVN-Kubernetes has changed to the interconnection scheme, which requires several steps related to OVN-Kubernetes to be changed, as there is no centralized OVN control plane that has to be converted into single-node.

Concretely, we have to replace steps 12, 13 and 14 with the following steps:

12. If you are using OVNKubernetes network plugin, restart ovnkube-controlplane pods

• Delete all the ovnkube-controlplane pods by running the following command

  oc -n openshift-ovn-kubernetes delete pod -l app=ovnkube-control-plane
  

• Ensure that all the ovnkube-controlplane pods are deployed again by running the following command

  oc -n openshift-ovn-kubernetes get pod -l app=ovnkube-control-plane
  

13. If you are using OVNKubernetes network plugin, restart the Open Virtual Network (OVN) Kubernetes pods on all the nodes one by one. Restart it first the recovery control plane host, then the other control plane hosts (if available), then the other nodes. Steps to restart it in each node are as follows:

• Remove the northbound database (nbdb) and southbound database (sbdb). Access the node by using Secure Shell (SSH) and run the following command:

  sudo rm -f /var/lib/ovn-ic/etc/*.db
  

• Restart the OpenVSwitch services. Access the node by using Secure Shell (SSH) and run the following command:

  sudo systemctl restart ovs-vswitchd ovsdb-server
  

• Delete the ovnkube-node pod running on the node by running the following command (replace ${node} with the name of the node):

  oc -n openshift-ovn-kubernetes delete pod -l app=ovnkube-node --field-selector=spec.nodeName==${node}
  

• Ensure that the ovnkube-node pod is running again (it may take several minutes)

  oc -n openshift-ovn-kubernetes get pod -l app=ovnkube-node --field-selector=spec.nodeName==${node}