Skip to content

Commit ffbd6eb

Browse files
committed
updated OSD and ROSA descriptions to remove ROSA from OSD docs
1 parent cda9024 commit ffbd6eb

File tree

3 files changed

+9
-5
lines changed

3 files changed

+9
-5
lines changed

modules/osd-aws-privatelink-firewall-prerequisites.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,12 @@
77
[id="osd-aws-privatelink-firewall-prerequisites_{context}"]
88
= AWS firewall prerequisites
99

10+
ifdef::openshift-rosa[]
1011
[IMPORTANT]
1112
====
1213
Only ROSA clusters deployed with PrivateLink can use a firewall to control egress traffic.
1314
====
15+
endif::[]
1416

1517
This section provides the necessary details that enable you to control egress traffic from your {product-title} cluster. If you are using a firewall to control egress traffic, you must configure your firewall to grant access to the domain and port combinations below. {product-title} requires this access to provide a fully managed OpenShift service.
1618

modules/sd-planning-cluster-maximums.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,18 +4,18 @@
44
// * rosa_planning/rosa-limits-scalability.adoc
55

66
[id="tested-cluster-maximums-sd_{context}"]
7-
= ROSA tested cluster maximums
7+
= Cluster maximums
88

99
Consider the following tested object maximums when you plan a {product-title}
1010
ifdef::openshift-rosa[]
11-
(ROSA)
11+
(ROSA)
1212
endif::[]
13-
cluster installation. The table specifies the maximum limits for each tested type in a
13+
cluster installation. The table specifies the maximum limits for each tested type in a
1414
ifdef::openshift-rosa[]
15-
(ROSA)
15+
(ROSA)
1616
endif::[]
1717
ifdef::openshift-dedicated[]
18-
{product-title}
18+
{product-title}
1919
endif::[]
2020
cluster.
2121

networking/cidr-range-definitions.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,10 +26,12 @@ OVN-Kubernetes, the default network provider in {product-title} 4.11 and later,
2626
== Machine CIDR
2727
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.
2828

29+
ifdef::openshift-rosa[]
2930
[NOTE]
3031
====
3132
When using {hcp-title}, the static IP address `172.20.0.1` is reserved for the internal Kubernetes API address. The machine, pod, and service CIDRs ranges must not conflict with this IP address.
3233
====
34+
endif::[]
3335

3436
[id="service-cidr-description"]
3537
== Service CIDR

0 commit comments

Comments
 (0)