We observed that when multiple NetworkAttachmentDefinitions (NADs) with the same name are created in different namespaces, OVN components may enter an unstable state (including CrashLoopBackOff).

OVN should be able to properly isolate namespace-scoped resources and must not fail or enter CrashLoopBackOff due to duplicate NAD names across namespaces.

Steps to Reproduce:
Create a NetworkAttachmentDefinition named <nad-name> in namespace A.

Create another NetworkAttachmentDefinition with the same name <nad-name> in namespace B.

Observe OVN behavior.

Actual Result:
OVN components become unstable / enter CrashLoopBackOff.

Networking inconsistencies observed.

Expected Result:
OVN should handle namespace-scoped NADs independently.

Duplicate NAD names across namespaces should not cause OVN instability.

No CrashLoopBackOff or control plane disruption should occur.

Impact:
This behavior can lead to:

Cluster networking instability

Production impact