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: specification/containerservice/resource-manager/Microsoft.ContainerService/aks/preview/2024-04-02-preview/managedClusters.json
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5101,7 +5101,8 @@
5101
5101
"loadBalancer",
5102
5102
"userDefinedRouting",
5103
5103
"managedNATGateway",
5104
-
"userAssignedNATGateway"
5104
+
"userAssignedNATGateway",
5105
+
"none"
5105
5106
],
5106
5107
"x-ms-enum": {
5107
5108
"name": "outboundType",
@@ -5122,6 +5123,10 @@
5122
5123
{
5123
5124
"value": "userAssignedNATGateway",
5124
5125
"description": "The user-assigned NAT gateway associated to the cluster subnet is used for egress. This is an advanced scenario and requires proper network configuration."
5126
+
},
5127
+
{
5128
+
"value": "none",
5129
+
"description": "The AKS cluster is not set with any outbound-type. All AKS nodes follows Azure VM default outbound behavior. Please refer to https://azure.microsoft.com/en-us/updates/default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access/"
0 commit comments