Skip to content

Commit ee174de

Browse files
author
Jill Grant
authored
Merge pull request #280152 from johnmarco/jm-aro-large-cluster-deployments
ARO: Large cluster deployment
2 parents 7d38b91 + 68875ed commit ee174de

File tree

2 files changed

+62
-0
lines changed

2 files changed

+62
-0
lines changed
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Deploy a large Azure Red Hat OpenShift cluster
3+
description: Discover how to deploy a large Azure Red Hat OpenShift cluster.
4+
author: johnmarco
5+
ms.author: johnmarc
6+
ms.service: azure-redhat-openshift
7+
ms.topic: article
8+
ms.date: 08/15/2024
9+
---
10+
# Deploy a large Azure Red Hat OpenShift cluster
11+
12+
This article provides the steps and best practices for deploying large scale Azure Red Hat OpenShift clusters up to 250 nodes. For clusters of that size, a combination of control plane nodes and infrastructure nodes is needed to ensure the cluster functions properly is recommended.
13+
14+
> [!CAUTION]
15+
> Before deleting a large cluster, descale the cluster to 120 nodes or below.
16+
>
17+
18+
## Deploy a cluster
19+
20+
For clusters with over 101 control plane nodes, use the following [virtual machine instance types](support-policies-v4.md#supported-virtual-machine-sizes) size recommendations (or similar, newer generation instance types):
21+
22+
- Standard_D32s_v3
23+
- Standard_D32s_v4
24+
- Standard_D32s_v5
25+
26+
Following is a sample script using Azure CLI to deploy a cluster with Standard_D32s_v5 as the control plane node:
27+
28+
```azurecli
29+
#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+
```
31+
32+
## Deploy infrastructure nodes for the cluster
33+
34+
For clusters with over 101 nodes, infrastructure nodes are required to separate cluster workloads (such as prometheus) to minimize contention with other workloads.
35+
36+
> [!NOTE]
37+
> It's recommended that you deploy three (3) infrastructure nodes per cluster for redundancy and scalability needs.
38+
>
39+
40+
The following instance types are recommended for infrastructure nodes:
41+
42+
- Standard_E16as_v5
43+
- Standard_E16s_v5
44+
45+
For instructions on configuring infrastructure nodes, see [Deploy infrastructure nodes in an Azure Red Hat OpenShift cluster](howto-infrastructure-nodes.md).
46+
47+
## Add IP addresses to the cluster
48+
49+
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 250 nodes requires a minimum of four (4) IP addresses.
50+
51+
To add IP addresses to the load balancer using Azure CLI, run the following command:
52+
53+
`az aro update -n [clustername] –g [resourcegroup] --lb-ip-count 20`
54+
55+
To add IP addresses through a rest API call:
56+
57+
```rest
58+
az rest --method patch --url https://management.azure.com/subscriptions/fe16a035-e540-4ab7-80d9-373fa9a3d6ae/resourceGroups/shared-cluster/providers/Microsoft.RedHatOpenShift/OpenShiftClusters/shared-cluster?api-version=2023-07-01-preview --body '{"properties": {"networkProfile": {"loadBalancerProfile": {"managedOutboundIps": {"count": 5}}}}}' --headers "Content-Type=application/json"
59+
```
60+

articles/openshift/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,8 @@
3232
href: quickstart-openshift-arm-bicep-template.md
3333
- name: Upgrade an Azure Red Hat OpenShift cluster
3434
href: howto-upgrade.md
35+
- name: Deploy large Azure Red Hat OpenShift clusters spot nodes
36+
href: howto-large-clusters.md
3537
- name: Use spot nodes
3638
href: howto-spot-nodes.md
3739
- name: Deploy infrastructure nodes

0 commit comments

Comments
 (0)