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/api-server-authorized-ip-ranges.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The *API server authorized IP ranges* feature has the following limitations:
26
26
27
27
- The *API server authorized IP ranges* feature was moved out of preview in October 2019. For clusters created after the feature was moved out of preview, this feature is only supported on the *Standard* SKU load balancer. Any existing clusters on the *Basic* SKU load balancer with the *API server authorized IP ranges* feature enabled will continue to work as is. However, these clusters cannot be migrated to a *Standard* SKU load balancer. Existing clusters will continue to work if the Kubernetes version and control plane are upgraded.
28
28
- The *API server authorized IP ranges* feature isn't supported on private clusters.
29
-
- When using this feature with clusters that use [Node Public IP](use-multiple-node-pools.md#assign-a-public-ip-per-node-for-your-node-pools), the node pools using Node Public IP must use public IP prefixes. The public IP prefixes must be added as authorized ranges.
29
+
- When using this feature with clusters that use [Node Public IP](use-node-public-ips.md), the node pools using Node Public IP must use public IP prefixes. The public IP prefixes must be added as authorized ranges.
Copy file name to clipboardExpand all lines: articles/aks/use-node-public-ips.md
+74-19Lines changed: 74 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,15 +56,33 @@ Finally, when creating a new cluster or adding a new node pool, use the flag `no
56
56
az aks create -g MyResourceGroup3 -n MyManagedCluster -l eastus --enable-node-public-ip --node-public-ip-prefix /subscriptions/<subscription-id>/resourcegroups/MyResourceGroup3/providers/Microsoft.Network/publicIPPrefixes/MyPublicIPPrefix
57
57
```
58
58
59
+
## Locate public IPs for nodes
60
+
61
+
You can locate the public IPs for your nodes in various ways:
62
+
63
+
* Use the Azure CLI command [az vmss list-instance-public-ips][az-list-ips].
64
+
* Use [PowerShell or Bash commands][vmss-commands].
65
+
* You can also view the public IPs in the Azure portal by viewing the instances in the Virtual Machine Scale Set.
66
+
67
+
> [!Important]
68
+
> The [node resource group][node-resource-group] contains the nodes and their public IPs. Use the node resource group when executing commands to find the public IPs for your nodes.
69
+
70
+
```azurecli
71
+
az vmss list-instance-public-ips -g MC_MyResourceGroup2_MyManagedCluster_eastus -n YourVirtualMachineScaleSetName
72
+
```
73
+
59
74
## Use public IP tags on node public IPs (PREVIEW)
60
75
61
76
Public IP tags can be utilized on node public IPs to utilize the [Azure Routing Preference](/azure/virtual-network/ip-services/routing-preference-overview.md) feature.
62
77
63
78
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
64
79
65
-
### Install the aks-preview Azure CLI extension
80
+
### Requirements
66
81
67
-
Version 0.5.115 of the aks-preview extension is required.
82
+
* AKS version 1.24 or greater is required.
83
+
* Version 0.5.115 of the aks-preview extension is required.
84
+
85
+
### Install the aks-preview Azure CLI extension
68
86
69
87
To install the aks-preview extension, run the following command:
70
88
@@ -114,22 +132,7 @@ az aks nodepool add --cluster-name <clusterName> -n <nodepoolName> -l <location>
114
132
--node-public-ip-tags RoutingPreference=Internet
115
133
```
116
134
117
-
## Locate public IPs for nodes
118
-
119
-
You can locate the public IPs for your nodes in various ways:
120
-
121
-
* Use the Azure CLI command [az vmss list-instance-public-ips][az-list-ips].
122
-
* Use [PowerShell or Bash commands][vmss-commands].
123
-
* You can also view the public IPs in the Azure portal by viewing the instances in the Virtual Machine Scale Set.
124
-
125
-
> [!Important]
126
-
> The [node resource group][node-resource-group] contains the nodes and their public IPs. Use the node resource group when executing commands to find the public IPs for your nodes.
127
-
128
-
```azurecli
129
-
az vmss list-instance-public-ips -g MC_MyResourceGroup2_MyManagedCluster_eastus -n YourVirtualMachineScaleSetName
130
-
```
131
-
132
-
## Allow host port connections and add node pools to application security groups
135
+
## Allow host port connections and add node pools to application security groups (PREVIEW)
133
136
134
137
AKS nodes utilizing node public IPs that host services on their host address need to have an NSG rule added to allow the traffic. Adding the desired ports in the node pool configuration will create the appropriate allow rules in the cluster network security group.
135
138
@@ -295,6 +298,7 @@ spec:
295
298
```
296
299
297
300
When the deployment is applied, the `hostPort` entries will be in the YAML of the individual pods:
301
+
298
302
```shell
299
303
$ kubectl describe pod echoserver-hostport-75dc8d8855-4gjfc
0 commit comments