Skip to content

Commit 3a55e44

Browse files
committed
Draft of new article
1 parent cbd7165 commit 3a55e44

File tree

2 files changed

+58
-0
lines changed

2 files changed

+58
-0
lines changed
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
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: 07/05/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 180 nodes. For clusters of that size, a combination of control plane nodes and infrastructure nodes to ensure the cluster functions properly.
13+
14+
## Deploy a cluster
15+
16+
For clusters with over 101 nodes, use the following [virtual machine instance types](support-policies-v4.md#supported-virtual-machine-sizes) size recommendations (or similar, newer generation instance types):
17+
18+
- Standard_D32s_v3
19+
- Standard_D32s_v4
20+
- Standard_D32s_v5
21+
22+
Following is a sample script using Azure CLI to deploy a cluster with Standard_D32s_v5 as the control plane nodes:
23+
24+
```azurecli
25+
#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
26+
```
27+
28+
## Deploy infrastructure nodes for the cluster
29+
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+
32+
> [!NOTE]
33+
> It's recommended that you deploy 3 infrastructure nodes per cluster for redundancy and scalability needs.
34+
>
35+
36+
The following instance types are recommended for infrastructure nodes:
37+
38+
- Standard_E16as_v5
39+
- Standard_E16s_v5
40+
41+
For instructions on configuring infrastructure nodes, see [Deploy infrastructure nodes in an Azure Red Hat OpenShift (ARO) cluster](howto-infrastructure-nodes.md).
42+
43+
## Add IP addresses to the cluster
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.
46+
47+
To add IP addresses to the load balancer using Azure CLI, run the following:
48+
49+
`az aro update -n [clustername] –g [resourcegroup] --lb-ip-count 20`
50+
51+
To add IP addresses through a rest API call:
52+
53+
```rest
54+
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"
55+
```
56+

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 ARO 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)