Description of problem (please be detailed as possible and provide log
snippets):

Customer is going to deploy ACM/ODF/RDR to managed clusters using openshift-SDN, will there be any impact changes needed when migrating to OVN-kubernetes in the future?

Version of all relevant components (if applicable):

4.14 ODF/OCP
ACM 2.9
openshift-SDN

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Yes

Is there any workaround available to the best of your knowledge?

NA

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

5

Can this issue reproducible?

Always

Can this issue reproduce from the UI?

NA

If this is a regression, please provide more details to justify this:

Steps to Reproduce:

1. Deploy ACM/ODF/RDR following [1] to managed OCP nodes that are running `openshift-SDN`
2. Migrate all from `openshift-SDN` to `OVN-kubernetes`
3.

Actual results:

Everything should work as intended between configurations both SDN

Expected results:

Unknown, we need to know the impact when the SDN migration happens after setting up and configuring RDR for existing production environments.

Additional info:

Customer's managed clusters are also using the same subnet for both the primary/secondary networks. Although we have a suggestion to use `Globalnet` [2] to alleviate this, what happens if they deploy first using `openshift-SDN` then migrate to `OVN-kubernetes` ?

[1] https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.14/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index#rdr-solution

[2] https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.14/html-single/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/index#requirements-for-enabling-regional-disaster-recovery_rdr