You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/openshift/howto-large-clusters.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,11 @@ author: johnmarco
5
5
ms.author: johnmarc
6
6
ms.service: azure-redhat-openshift
7
7
ms.topic: article
8
-
ms.date: 07/05/2024
8
+
ms.date: 07/10/2024
9
9
---
10
10
# Deploy a large Azure Red Hat OpenShift cluster
11
11
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.
13
13
14
14
## Deploy a cluster
15
15
@@ -19,7 +19,7 @@ For clusters with over 101 nodes, use the following [virtual machine instance ty
19
19
- Standard_D32s_v4
20
20
- Standard_D32s_v5
21
21
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:
@@ -30,7 +30,7 @@ Following is a sample script using Azure CLI to deploy a cluster with Standard_D
30
30
For clusters with over 101 nodes, infrastructure nodes are required to separate cluster workloads (such as prometheus) to minimize contention with other workloads.
31
31
32
32
> [!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.
34
34
>
35
35
36
36
The following instance types are recommended for infrastructure nodes:
@@ -42,9 +42,9 @@ For instructions on configuring infrastructure nodes, see [Deploy infrastructure
42
42
43
43
## Add IP addresses to the cluster
44
44
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.
46
46
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:
48
48
49
49
`az aro update -n [clustername] –g [resourcegroup] --lb-ip-count 20`
0 commit comments