Skip to content

Commit 608d41a

Browse files
authored
Merge pull request #286628 from johnmarco/jm-aro-multiple-ips-update
ARO: Multiple IP edits
2 parents 26c05b7 + a873ed6 commit 608d41a

File tree

1 file changed

+19
-22
lines changed

1 file changed

+19
-22
lines changed
Lines changed: 19 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,17 @@
11
---
2-
title: Configure multiple IP addresses for ARO cluster load balancers
2+
title: Configure multiple IP addresses for Azure Red Hat OpenShift cluster load balancers
33
description: Discover how to configure multiple IP addresses for ARO cluster load balancers.
44
author: johnmarco
55
ms.author: johnmarc
66
ms.service: azure-redhat-openshift
77
ms.topic: how-to
8-
ms.date: 09/06/2024
8+
ms.date: 09/11/2024
9+
910
#Customer intent: As an ARO SRE, I need to configure multiple outbound IP addresses per ARO cluster load balancers
1011
---
11-
# Configure multiple IP addresses per ARO cluster load balancer
12+
# Configure multiple IP addresses per Azure Red Hat OpenShift cluster load balancer
1213

13-
ARO public clusters are created with a public load balancer that's used for outbound connectivity from inside the cluster. By default, one public IP address is configured on that public load balancer, and that limits the maximum node count of your cluster to 65. To be able to scale your cluster to the maximum supported number of 250 nodes, you need to assign multiple additional public IP addresses to the load balancer.
14+
Azure Red Hat OpenShift public clusters are created with a public load balancer that's used for outbound connectivity from inside the cluster. By default, one public IP address is configured on that public load balancer, and that limits the maximum node count of your cluster to 62. To be able to scale your cluster to the maximum supported number of 250 nodes, you need to assign multiple additional public IP addresses to the load balancer.
1415

1516
You can configure up to 20 IP addresses per cluster. The outbound rules and frontend IP configurations are adjusted to accommodate the number of IP addresses.
1617

@@ -22,9 +23,9 @@ You can configure up to 20 IP addresses per cluster. The outbound rules and fron
2223

2324
The multiple public IPs feature is only available on the current network architecture used by ARO; older clusters don't support this feature. If your cluster was created before OpenShift Container Platform (OCP) version 4.5, this feature isn't available even if you upgraded your OCP version since then.
2425

25-
If you're unsure if your cluster was created before the current version of OCP, use the following commands to check.
26+
If you're unsure if your cluster was created before OCP version 4.5, use the following commands to check.
2627

27-
To get the cluster managed resource group:
28+
Get the cluster managed resource group:
2829

2930
```
3031
RESOURCEGROUP=aro-rg # the name of the resource group your cluster is in
@@ -40,32 +41,28 @@ az network lb list -g $CLUSTER_RESOURCEGROUP -o table
4041

4142
If you have a loadbalancer named `$CLUSTER-public-lb`, the cluster has the older network architecture and can't use the multiple public IP feature.
4243

43-
<!--
44-
### Download ARO extension wheel file (Preview only)
45-
46-
In order to run the commands in this article, you must first download the ARO extension wheel file from [https://aka.ms/az-aroext-latest](https://aka.ms/az-aroext-latest). To install the extension, run the following command:
47-
48-
`az extension add -s <path to downloaded whl file>`
49-
-->
50-
5144
## Create the cluster with multiple IP addresses
5245

53-
To create a new ARO cluster with multiple managed IPs on the public load balancer, use the following command with the desired number of IPs in the `--load-balancer-managed-outbound-ip-count` parameter. In the example below, seven (7) IP addresses will be created:
46+
To create a new ARO cluster with multiple managed IPs on the public load balancer, use the following command with the desired number of IPs in the `--load-balancer-managed-outbound-ip-count` parameter. In the example below, seven (7) IP addresses are created:
5447

5548
```
56-
az aro create --resource-group aroResourceGroup --name aroCluster \
57-
58-
--load-balancer-managed-outbound-ip-count 7 \
49+
az aro create \
50+
--resource-group aroResourceGroup \
51+
--name aroCluster \
52+
--load-balancer-managed-outbound-ip-count 7
5953
```
6054

55+
See [Deploy a large Azure Red Hat OpenShift cluster](howto-large-clusters.md) for more information about deploying a large cluster.
56+
6157
## Update the number of IP addresses on existing clusters
6258

6359
To update the number of managed IPs on the public load balancer of an existing ARO cluster, use the following command with the desired number of IPs in the `--load-balancer-managed-outbound-ip-count` parameter. In the example below, the number of IPs for the cluster will be updated to four (4):
6460

6561
```
66-
az aro update --resource-group aroResourceGroup --name aroCluster \
67-
68-
--load-balancer-managed-outbound-ip-count 4
62+
az aro update \
63+
--resource-group aroResourceGroup \
64+
--name aroCluster \
65+
--load-balancer-managed-outbound-ip-count 4
6966
```
7067

71-
You can use this update method to either increase or decrease the number of IPs on a cluster to be between 1 and 20. Note that scaling down the number of clusters can interrupt the outbound network traffic from the cluster.
68+
You can use this update method to either increase or decrease the number of IPs on a cluster to be between 1 and 20. Scaling down the number of clusters can interrupt the outbound network traffic from the cluster.

0 commit comments

Comments
 (0)