hybrid-overlay on Windows nodes ignores existing non-persistent routes when creating the new vNIC. This becomes an issue especially on AWS where non-persistent routes are used for the local metadata server which is in turn used by the kubelet.
How reproducible:{code:none}
Always on Windows Server 2022 instances on AWS

1. Bring up an hybrid-ovn OCP cluster on AWS
2. Add a Windows Server 2022 Machine or BYOH instance

The Windows Server 2022 node goes to NotReady

The Windows Server 2022 node goes to Ready

While this problem shows up only on AWS, it can be an issue on other providers if customers are depending on non-persistent routes on Windows nodes in general.