-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem: Unable to create UDN on a HCP (kubevirt) cluster unless a custom Join Subnet is used
Version-Release number of selected component (if applicable): 4.18
How reproducible: Always
Details
When a udn with any subnet value it always throws the following error
apiVersion: k8s.ovn.org/v1 kind: UserDefinedNetwork metadata: creationTimestamp: '2025-04-06T08:12:55Z' finalizers: - k8s.ovn.org/user-defined-network-protection generation: 1 name: udn-1 namespace: hchaturv-udn-test resourceVersion: '22591' uid: 60d4556c-1d22-4c2e-b224-ab4628d1f5de spec: layer2: role: Primary subnets: - 192.164.0.0/16 topology: Layer2 status: conditions: - lastTransitionTime: '2025-04-06T08:12:55Z' message: 'failed to generate NetworkAttachmentDefinition: failed to render CNI network config: invalid subnet configuration: pod or join subnet overlaps with already configured internal subnets: illegal network configuration: user defined join subnet "100.65.0.0/16" overlaps built-in join subnet "100.65.0.0/16"' reason: SyncError status: 'False' type: NetworkCreated
The same happens in the layer3 as well.