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/aks/egress-outboundtype.md
+19-22Lines changed: 19 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
---
2
2
title: Customize cluster egress with outbound types in Azure Kubernetes Service (AKS)
3
-
description: Learn how to define a custom egress route in Azure Kubernetes Service (AKS)
3
+
description: Learn how to define a custom egress route in Azure Kubernetes Service (AKS).
4
4
author: asudbring
5
5
ms.subservice: aks-networking
6
6
ms.custom:
7
7
ms.author: allensu
8
8
ms.topic: how-to
9
-
ms.date: 02/06/2024
9
+
ms.date: 04/29/2024
10
10
#Customer intent: As a cluster operator, I want to define my own egress paths with user-defined routes. Since I define this up front I do not want AKS provided load balancer configurations.
11
11
---
12
12
13
13
# Customize cluster egress with outbound types in Azure Kubernetes Service (AKS)
14
14
15
-
You can customize egress for an AKS cluster to fit specific scenarios. By default, AKS will provision a standard SKU load balancer to be set up and used for egress. However, the default setup may not meet the requirements of all scenarios if public IPs are disallowed or additional hops are required for egress.
15
+
You can customize egress for an AKS cluster to fit specific scenarios. By default, AKS provisions a standard SKU load balancer to be set up and used for egress. However, the default setup may not meet the requirements of all scenarios if public IPs are disallowed or extra hops are required for egress.
16
16
17
17
This article covers the various types of outbound connectivity that are available in AKS clusters.
18
18
@@ -21,7 +21,7 @@ This article covers the various types of outbound connectivity that are availabl
21
21
22
22
## Limitations
23
23
24
-
* Setting `outboundType` requires AKS clusters with a `vm-set-type` of `VirtualMachineScaleSets` and `load-balancer-sku` of `Standard`.
24
+
- Setting `outboundType` requires AKS clusters with a `vm-set-type` of `VirtualMachineScaleSets` and `load-balancer-sku` of `Standard`.
25
25
26
26
## Outbound types in AKS
27
27
@@ -36,9 +36,9 @@ The load balancer is used for egress through an AKS-assigned public IP. An outbo
36
36
37
37
If `loadBalancer` is set, AKS automatically completes the following configuration:
38
38
39
-
* A public IP address is provisioned for cluster egress.
40
-
* The public IP address is assigned to the load balancer resource.
41
-
* Backend pools for the load balancer are set up for agent nodes in the cluster.
39
+
- A public IP address is provisioned for cluster egress.
40
+
- The public IP address is assigned to the load balancer resource.
41
+
- Backend pools for the load balancer are set up for agent nodes in the cluster.
42
42
43
43
44
44
@@ -48,8 +48,8 @@ For more information, see [using a standard load balancer in AKS](load-balancer-
48
48
49
49
If `managedNatGateway` or `userAssignedNatGateway` are selected for `outboundType`, AKS relies on [Azure Networking NAT gateway](../virtual-network/nat-gateway/manage-nat-gateway.md) for cluster egress.
50
50
51
-
* Select `managedNatGateway` when using managed virtual networks. AKS will provision a NAT gateway and attach it to the cluster subnet.
52
-
* Select `userAssignedNatGateway` when using bring-your-own virtual networking. This option requires that you have provisioned a NAT gateway before cluster creation.
51
+
- Select `managedNatGateway` when using managed virtual networks. AKS provisions a NAT gateway and attach it to the cluster subnet.
52
+
- Select `userAssignedNatGateway` when using bring-your-own virtual networking. This option requires that you have provisioned a NAT gateway before cluster creation.
53
53
54
54
For more information, see [using NAT gateway with AKS](nat-gateway.md).
55
55
@@ -72,10 +72,10 @@ The following tables show the supported migration paths between outbound types f
@@ -131,24 +131,21 @@ az aks update -g <resourceGroup> -n <clusterName> --outbound-type userDefinedRou
131
131
132
132
### Update cluster from loadbalancer to userAssignedNATGateway in BYO vnet scenario
133
133
134
-
- Associate nat gateway with subnet where the workload is associated with. Please refer to [Create a managed or user-assigned NAT gateway](nat-gateway.md)
134
+
- Associate nat gateway with subnet where the workload is associated with. Refer to [Create a managed or user-assigned NAT gateway](nat-gateway.md)
135
135
136
136
```azurecli-interactive
137
137
az aks update -g <resourceGroup> -n <clusterName> --outbound-type userAssignedNATGateway
138
138
```
139
139
140
140
## Next steps
141
141
142
-
*[Configure standard load balancing in an AKS cluster](load-balancer-standard.md)
143
-
*[Configure NAT gateway in an AKS cluster](nat-gateway.md)
144
-
*[Configure user-defined routing in an AKS cluster](egress-udr.md)
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments