ovnkube-node pod on CrashLoopBackOff while upgrading OpenShift to 4.18

Issue

• While upgrading OpenShift to 4.18 new ovnkube-node pods are on CrashLoopBackOff and the upgrade is not progressing :

$ oc get pods -n openshift-ovn-kubernetes
NAME                                     READY   STATUS             RESTARTS       AGE
ovnkube-control-plane-5fbdd85849-qrdgg   2/2     Running            0              162m
ovnkube-control-plane-5fbdd85849-zgr4r   2/2     Running            1 (149m ago)   162m
ovnkube-node-57hzk                       8/8     Running            0              142m
ovnkube-node-8mmn7                       8/8     Running            0              161m
ovnkube-node-8nbxt                       8/8     Running            0              160m
ovnkube-node-ggmwx                       8/8     Running            0              161m
ovnkube-node-jg7r9                       7/8     CrashLoopBackOff   5 (110s ago)   6m55s

• ovnkube-controller container reports the following error:

E0515 14:12:09.597194  215124 reflector.go:158] "Unhandled Error" err="github.com/k8snetworkplumbingwg/network-attachment-definition-client/pkg/client/informers/externalversions/factory.go:117: Failed to watch *v1.NetworkAttachmentDefinition: failed to list *v1.NetworkAttachmentDefinition: the server could not find the requested resource (get network-attachment-definitions.k8s.cni.cncf.io)" logger="UnhandledError"