Skip to content

Commit 79e3dbc

Browse files
committed
Copyedits
1 parent 3a55e44 commit 79e3dbc

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/openshift/howto-large-clusters.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ author: johnmarco
55
ms.author: johnmarc
66
ms.service: azure-redhat-openshift
77
ms.topic: article
8-
ms.date: 07/05/2024
8+
ms.date: 07/10/2024
99
---
1010
# Deploy a large Azure Red Hat OpenShift cluster
1111

12-
This article provides the steps and best practices for deploying large scale Azure Red Hat OpenShift clusters up to 180 nodes. For clusters of that size, a combination of control plane nodes and infrastructure nodes to ensure the cluster functions properly.
12+
This article provides the steps and best practices for deploying large scale Azure Red Hat OpenShift clusters up to 180 nodes. For clusters of that size, a combination of control plane nodes and infrastructure nodes to ensure the cluster functions properly is recommended.
1313

1414
## Deploy a cluster
1515

@@ -19,7 +19,7 @@ For clusters with over 101 nodes, use the following [virtual machine instance ty
1919
- Standard_D32s_v4
2020
- Standard_D32s_v5
2121

22-
Following is a sample script using Azure CLI to deploy a cluster with Standard_D32s_v5 as the control plane nodes:
22+
Following is a sample script using Azure CLI to deploy a cluster with Standard_D32s_v5 as the control plane node:
2323

2424
```azurecli
2525
#az aro create \ --resource-group $RESOURCEGROUP \ --name $CLUSTER \ --vnet aro-vnet \ --master-subnet master-subnet \ --worker-subnet worker-subnet --master-vm-size Standard_D32s_v5
@@ -30,7 +30,7 @@ Following is a sample script using Azure CLI to deploy a cluster with Standard_D
3030
For clusters with over 101 nodes, infrastructure nodes are required to separate cluster workloads (such as prometheus) to minimize contention with other workloads.
3131

3232
> [!NOTE]
33-
> It's recommended that you deploy 3 infrastructure nodes per cluster for redundancy and scalability needs.
33+
> It's recommended that you deploy three (3) infrastructure nodes per cluster for redundancy and scalability needs.
3434
>
3535
3636
The following instance types are recommended for infrastructure nodes:
@@ -42,9 +42,9 @@ For instructions on configuring infrastructure nodes, see [Deploy infrastructure
4242

4343
## Add IP addresses to the cluster
4444

45-
A maximum of 20 IP addresses can be added to a load balancer. One (1) OP addresses is needed per 65 nodes, so a cluster with 180 nodes requires a minimum of three (3) IP addresses.
45+
A maximum of 20 IP addresses can be added to a load balancer. One (1) IP address is needed per 65 nodes, so a cluster with 180 nodes requires a minimum of three (3) IP addresses.
4646

47-
To add IP addresses to the load balancer using Azure CLI, run the following:
47+
To add IP addresses to the load balancer using Azure CLI, run the following command:
4848

4949
`az aro update -n [clustername] –g [resourcegroup] --lb-ip-count 20`
5050

0 commit comments

Comments
 (0)