From 0f96233120d564069680164f553c6e1b8b2d8d97 Mon Sep 17 00:00:00 2001 From: dfitzmau Date: Thu, 14 May 2026 15:22:06 +0100 Subject: [PATCH] OCPBUGS-85437: Added subnet collision information to hcp-custom-ovn-subnets.adoc --- modules/hcp-custom-ovn-subnets.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/hcp-custom-ovn-subnets.adoc b/modules/hcp-custom-ovn-subnets.adoc index 836b0bf0420b..1297a454fa65 100644 --- a/modules/hcp-custom-ovn-subnets.adoc +++ b/modules/hcp-custom-ovn-subnets.adoc @@ -9,7 +9,7 @@ [role="_abstract"] In hosted clusters, you can configure internal OVN subnets to avoid routing conflicts, customize network architecture, or enable virtual private cloud (VPC) peering. -Avoid CIDR conflicts:: Connect VPCs that host {product-rosa} clusters with other VPCs that use the default OVN internal subnets of 100.88.0.0/16 and 100.64.0.0/16. +Avoid CIDR conflicts:: Connect VPCs that host {product-rosa} clusters with other VPCs that use the default OVN internal subnets of 100.88.0.0/16 and 100.64.0.0/16. To avoid a conflict on a `kubevirt` hosted cluster, the HyperShift Operator sets the OVN join subnet to `100.66.0.0./16` instead of `100.64.0.0./16` or `100.65.0.0/16`. The default CIDR for the OVN gateway router is `100.64.0.0./16`. The default CIDR for the user-defined network (UDN) join subnet is `100.65.0.0/16`. Customize network architecture:: Configure internal OVN subnets to align with your corporate network policies. Enable VPC peering:: Deploy hosted clusters in environments where default subnets conflict with peered networks.