Merge pull request #93269 from xenolinux/hcp-reserved-cidr

OCPBUGS#55102: Include reserved HCP CIDR ranges

Author: xenolinux

hosted_control_planes/hcp-prepare/hcp-requirements.adoc

@@ -22,3 +22,10 @@ include::modules/hcp-fips.adoc[leveloffset=+1]
 * link:https://access.redhat.com/articles/7099674[The {mce} 2.8 support matrix]
 * link:https://access.redhat.com/labs/ocpouic/?operator=multicluster-engine&&upgrade_path=4.14%20to%204.16[Red{nbsp}Hat {product-title} Operator Update Information Checker]
 * xref:../../hosted_control_planes/hcp-prepare/hcp-sizing-guidance.adoc#hcp-shared-infra_hcp-sizing-guidance[Shared infrastructure between hosted and standalone control planes]
+
+include::modules/hcp-cidr-ranges.adoc[leveloffset=+1]
+
+[role="_additional-resources"]
+.Additional resources
+
+* xref:../../networking/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions]

modules/hcp-cidr-ranges.adoc

@@ -0,0 +1,16 @@
+// Module included in the following assemblies:
+//
+// * hosted_control_planes/hcp-prepare/hcp-requirements.adoc
+
+:_mod-docs-content-type: REFERENCE
+[id="hcp-cidr-ranges_{context}"]
+= CIDR ranges for {hcp}
+
+For deploying {hcp} on {product-title}, use the following required Classless Inter-Domain Routing (CIDR) subnet ranges:
+
+* `v4InternalSubnet`: 100.65.0.0/16 (OVN-Kubernetes)
+* `clusterNetwork`: 10.132.0.0/14 (pod network)
+* `serviceNetwork`: 172.31.0.0/16
+
+
+For more information about {product-title} CIDR range definitions, see "CIDR range definitions".

networking/cidr-range-definitions.adoc

@@ -9,7 +9,7 @@ endif::openshift-dedicated,openshift-rosa[]
 
 toc::[]
 
-If your cluster uses OVN-Kubernetes, you must specify non-overlapping ranges for Classless Inter-Domain Routing (CIDR) subnet ranges.  
+If your cluster uses OVN-Kubernetes, you must specify non-overlapping ranges for Classless Inter-Domain Routing (CIDR) subnet ranges.
 
 [IMPORTANT]
 ====
@@ -18,9 +18,9 @@ For {product-title} 4.17 and later versions, clusters use `169.254.0.0/17` for I
 
 The following subnet types and 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. 
+* 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.
 * Masquerade: Prevents collisions for identical source and destination IP addresses that are sent from a node as hairpin traffic to the same node after a load balancer makes a routing decision.
-* Transit: A transit switch is a type of distributed switch that spans across all nodes in the cluster. A transit switch routes traffic between different zones. 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 transit switch. 
+* Transit: A transit switch is a type of distributed switch that spans across all nodes in the cluster. A transit switch routes traffic between different zones. 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 transit switch.
 
 [NOTE]
 ====
@@ -121,4 +121,7 @@ endif::openshift-rosa,openshift-dedicated[]
 
 ifdef::openshift-enterprise[]
 For example, if the host prefix is set to `/23`, each machine is assigned a `/23` subnet from the pod CIDR address range. The default is `/23`, allowing 510 cluster nodes, and 510 pod IP addresses per node.
-endif::openshift-enterprise[]
+endif::openshift-enterprise[]
+
+
+include::modules/hcp-cidr-ranges.adoc[leveloffset=+1]