Skip to content

Commit 24875ff

Browse files
Merge pull request #264043 from chasewilson/chase/IpBasedLoadbalancerGA
IP-Based Loadbalancer GA
2 parents 0506ad0 + 39a8f6e commit 24875ff

File tree

1 file changed

+2
-37
lines changed

1 file changed

+2
-37
lines changed

articles/aks/load-balancer-standard.md

Lines changed: 2 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to use a public load balancer with a Standard SKU to expo
55
ms.subservice: aks-networking
66
ms.custom: devx-track-azurecli
77
ms.topic: how-to
8-
ms.date: 10/30/2023
8+
ms.date: 01/23/2024
99
ms.author: allensu
1010
author: asudbring
1111
#Customer intent: As a cluster operator or developer, I want to learn how to create a service in AKS that uses an Azure Load Balancer with a Standard SKU.
@@ -125,7 +125,7 @@ You can customize different settings for your standard public load balancer at c
125125
> [!IMPORTANT]
126126
> Only one outbound IP option (managed IPs, bring your own IP, or IP prefix) can be used at a given time.
127127

128-
### Change the inbound pool type (PREVIEW)
128+
### Change the inbound pool type
129129

130130
AKS nodes can be referenced in the load balancer backend pools by either their IP configuration (Azure Virtual Machine Scale Sets based membership) or by their IP address only. Utilizing the IP address based backend pool membership provides higher efficiencies when updating services and provisioning load balancers, especially at high node counts. Provisioning new clusters with IP based backend pools and converting existing clusters is now supported. When combined with NAT Gateway or user-defined routing egress types, provisioning of new nodes and services are more performant.
131131

@@ -136,48 +136,13 @@ Two different pool membership types are available:
136136

137137
#### Requirements
138138

139-
* The `aks-preview` extension must be at least version 0.5.103.
140139
* The AKS cluster must be version 1.23 or newer.
141140
* The AKS cluster must be using standard load balancers and virtual machine scale sets.
142141

143142
#### Limitations
144143

145144
* Clusters using IP based backend pools are limited to 2500 nodes.
146145

147-
[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
148-
149-
#### Install the aks-preview CLI extension
150-
151-
```azurecli-interactive
152-
# Install the aks-preview extension
153-
az extension add --name aks-preview
154-
155-
# Update the extension to make sure you have the latest version installed
156-
az extension update --name aks-preview
157-
```
158-
159-
#### Register the `IPBasedLoadBalancerPreview` preview feature
160-
161-
To create an AKS cluster with IP based backend pools, you must enable the `IPBasedLoadBalancerPreview` feature flag on your subscription.
162-
163-
Register the `IPBasedLoadBalancerPreview` feature flag by using the `az feature register` command, as shown in the following example:
164-
165-
```azurecli-interactive
166-
az feature register --namespace "Microsoft.ContainerService" --name "IPBasedLoadBalancerPreview"
167-
```
168-
169-
It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
170-
171-
```azurecli-interactive
172-
az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/IPBasedLoadBalancerPreview')].{Name:name,State:properties.state}"
173-
```
174-
175-
When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
176-
177-
```azurecli-interactive
178-
az provider register --namespace Microsoft.ContainerService
179-
```
180-
181146
#### Create a new AKS cluster with IP-based inbound pool membership
182147

183148
```azurecli-interactive

0 commit comments

Comments
 (0)