Skip to content

Commit 9b448a7

Browse files
authored
Merge pull request #52724 from EricPonvelle/OSDOCS-4401_CIDR-clarity
OSDOCS-4401: Added clarity for CIDR ranges
2 parents d97bada + fef8704 commit 9b448a7

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

networking/cidr-range-definitions.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,10 @@ You must specify non-overlapping ranges for the following CIDR ranges.
1313
Machine CIDR ranges cannot be changed after creating your cluster.
1414
====
1515

16+
ifdef::openshift-rosa,openshift-dedicated[]
17+
When specifying subnet CIDR ranges, ensure that the subnet CIDR range is within the defined Machine CIDR. You must verify that the subnet CIDR ranges allow for enough IP addresses for all intended workloads, including at least eight IP addresses for possible AWS Load Balancers.
18+
endif::[]
19+
1620
[id="machine-cidr-description"]
1721
== Machine CIDR
1822
In the Machine CIDR field, you must specify the IP address range for machines or cluster nodes. This range must encompass all CIDR address ranges for your virtual private cloud (VPC) subnets. Subnets must be contiguous. A minimum IP address range of 128 addresses, using the subnet prefix `/25`, is supported for single availability zone deployments. A minimum address range of 256 addresses, using the subnet prefix `/24`, is supported for deployments that use multiple availability zones. The default is `10.0.0.0/16`. This range must not conflict with any connected networks.

0 commit comments

Comments
 (0)