Skip to content

Commit 8499f31

Browse files
committed
SME review edits
1 parent f1c1929 commit 8499f31

File tree

1 file changed

+8
-3
lines changed

1 file changed

+8
-3
lines changed

articles/openshift/howto-large-clusters.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -49,12 +49,12 @@ This can be accomplished as part of the cluster creation process or later, after
4949
When deploying a large cluster, you must start with at most 50 worker nodes at creation time, then scale the cluster out to the desired number of worker nodes, up to 250 worker nodes.
5050

5151
> [!NOTE]
52-
> While you can define up to 50 worker nodes at creation time, it's best to start with a small cluster (e.g, three (3) worker nodes as the default) and then scale to the desired number of worker nodes after the cluster is installed.
52+
> While you can define up to 50 worker nodes at creation time, it's best to start with a small cluster (e.g, three (3) worker nodes) and then scale out to the desired number of worker nodes after the cluster is installed.
5353
>
5454
5555
Follow the steps provided in [Create an Azure Red Hat OpenShift cluster](https://learn.microsoft.com/azure/openshift/create-cluster?tabs=azure-cli) until the "Create the cluster" steps, then continue as instructed:
5656

57-
For large clusters, the previous recommendations should be followed. Therefore, the sample command below using the Azure CLI can be used to deploy a cluster with Standard_D32s_v5 as the control plane nodes, requesting three public IP addresses, and defining nine worker nodes:
57+
The sample command below using the Azure CLI can be used to deploy a cluster with Standard_D32s_v5 as the control plane nodes, requesting three public IP addresses, and defining nine worker nodes:
5858

5959
```azurecli
6060
az aro create \
@@ -70,7 +70,12 @@ az aro create \
7070

7171
To add IP addresses to the load balancer using the Azure CLI after the cluster is created, run the following command:
7272

73-
`az aro update --name <CLUSTER_NAME> –-resource-group <RESOURCE_GROUP> --lb-ip-count <PUBLIC_IP_COUNT>`
73+
```azurecli
74+
az aro update
75+
--name <CLUSTER_NAME>
76+
–-resource-group <RESOURCE_GROUP>
77+
--lb-ip-count <PUBLIC_IP_COUNT>`
78+
```
7479

7580
You can then configure the corresponding OpenShift MachineSets to obtain the number of worker nodes desired. See [Manually scaling a compute machine set](https://docs.openshift.com/container-platform/latest/machine_management/manually-scaling-machineset.html) for more details.
7681

0 commit comments

Comments
 (0)