From 91681b0a3fd372294492c5016f1bcd6c44ebd02c Mon Sep 17 00:00:00 2001 From: dfitzmau Date: Fri, 20 Mar 2026 17:01:09 +0000 Subject: [PATCH] OSDOCS-18665-16: CP review for CORE-1 --- networking/cidr-range-definitions.adoc | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/networking/cidr-range-definitions.adoc b/networking/cidr-range-definitions.adoc index c21b433a79ef..541c29419892 100644 --- a/networking/cidr-range-definitions.adoc +++ b/networking/cidr-range-definitions.adoc @@ -12,18 +12,6 @@ toc::[] [role="_abstract"] To ensure stable and accurate network routing in {product-title} clusters that use OVN-Kubernetes, define non-overlapping Classless Inter-Domain Routing (CIDR) subnet ranges. Establishing unique ranges prevents IP address conflicts so that internal traffic reaches its intended destination without interference. -[IMPORTANT] -==== -For {product-title} 4.17 and later versions, clusters use `169.254.0.0/17` for IPv4 and `fd69::/112` for IPv6 as the default masquerade subnet. You must avoid these ranges. For upgraded clusters, there is no change to the default masquerade subnet. -==== - -[TIP] -==== -You can use the link:https://access.redhat.com/labs/ocpnc/[Red Hat OpenShift Network Calculator] to decide your networking needs before setting CIDR range during cluster creation. - -You must have a Red Hat account to use the calculator. -==== - The following subnet types are mandatory for a cluster that uses OVN-Kubernetes: * Join: Uses a join switch to connect gateway routers to distributed routers. A join switch reduces the number of IP addresses for a distributed router. For a cluster that uses the OVN-Kubernetes plugin, an IP address from a dedicated subnet is assigned to any logical port that attaches to the join switch.