Skip to content

Commit 17dfad1

Browse files
authored
Merge pull request #89841 from dfitzmau/OCPBUGS-44288-15-ent
[enterprise-4.15] Ocpbugs-44288-15-ent
2 parents e875646 + 397ab16 commit 17dfad1

File tree

1 file changed

+39
-3
lines changed

1 file changed

+39
-3
lines changed

networking/cidr-range-definitions.adoc

Lines changed: 39 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,25 +9,54 @@ endif::openshift-dedicated,openshift-rosa[]
99

1010
toc::[]
1111

12-
You must specify non-overlapping ranges for the following CIDR ranges.
12+
If your cluster uses OVN-Kubernetes, you must specify non-overlapping ranges for Classless Inter-Domain Routing (CIDR) subnet ranges.
13+
14+
The following subnet types are mandatory for a cluster that uses OVN-Kubernetes:
15+
16+
* 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.
17+
* 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.
18+
* 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.
1319
1420
[NOTE]
1521
====
16-
Machine CIDR ranges cannot be changed after creating your cluster.
22+
You can change the join and transit CIDR ranges for your cluster as a post-installation task.
1723
====
1824

1925
ifdef::openshift-rosa,openshift-dedicated[]
2026
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 depending on which platform the cluster is hosted.
2127
endif::[]
2228

29+
OVN-Kubernetes, the default network provider in {product-title} 4.14 and later versions, internally uses the following IP address subnet ranges:
30+
31+
* `V4JoinSubnet`: `100.64.0.0/16`
32+
* `V6JoinSubnet`: `fd98::/64`
33+
* `V4TransitSwitchSubnet`: `100.88.0.0/16`
34+
* `V6TransitSwitchSubnet`: `fd97::/64`
35+
* `defaultV4MasqueradeSubnet`: `169.254.169.0/29`
36+
* `defaultV6MasqueradeSubnet`: `fd69::/125`
37+
2338
[IMPORTANT]
2439
====
25-
OVN-Kubernetes, the default network provider in {product-title} 4.14 and later versions, uses the following IP address ranges internally: `100.64.0.0/16`, `169.254.169.0/29`, `100.88.0.0/16`, `fd98::/64`, `fd69::/125`, and `fd97::/64`. If your cluster uses OVN-Kubernetes, do not include any of these IP address ranges in any other CIDR definitions in your cluster or infrastructure.
40+
The previous list includes join, transit, and masquerade IPv4 and IPv6 address subnets. If your cluster uses OVN-Kubernetes, do not include any of these IP address subnet ranges in any other CIDR definitions in your cluster or infrastructure.
2641
====
2742

43+
ifndef::openshift-rosa,openshift-dedicated[]
44+
[role="_additional-resources"]
45+
.Additional resources
46+
47+
* For more information about configuring join subnets or transit subnets, see xref:../networking/ovn_kubernetes_network_provider/configure-ovn-kubernetes-subnets.adoc#configure-ovn-kubernetes-subnets[Configuring OVN-Kubernetes internal IP address subnets].
48+
endif::openshift-rosa,openshift-dedicated[]
49+
2850
[id="machine-cidr-description"]
2951
== Machine CIDR
52+
3053
In the Machine classless inter-domain routing (CIDR) field, you must specify the IP address range for machines or cluster nodes.
54+
55+
[NOTE]
56+
====
57+
Machine CIDR ranges cannot be changed after creating your cluster.
58+
====
59+
3160
ifdef::openshift-rosa,openshift-dedicated[]
3261
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.
3362
endif::openshift-rosa,openshift-dedicated[]
@@ -41,6 +70,13 @@ When using {hcp-title}, the static IP address `172.20.0.1` is reserved for the i
4170
====
4271
endif::[]
4372
73+
ifndef::openshift-rosa,openshift-dedicated[]
74+
[role="_additional-resources"]
75+
.Additional resources
76+
77+
* xref:../networking/cluster-network-operator.adoc#nw-operator-cr_cluster-network-operator[Cluster Network Operator configuration]
78+
endif::[]
79+
4480
[id="service-cidr-description"]
4581
== Service CIDR
4682
In the Service CIDR field, you must specify the IP address range for services.

0 commit comments

Comments
 (0)