Skip to content

Commit 82c3f20

Browse files
committed
Fix broken links and missing TOC
1 parent 684384f commit 82c3f20

File tree

3 files changed

+77
-20
lines changed

3 files changed

+77
-20
lines changed

articles/aks/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -248,6 +248,8 @@
248248
href: use-cvm.md
249249
- name: Use system node pools
250250
href: use-system-pools.md
251+
- name: Use instance-level public IP addresses
252+
href: use-node-public-ips.md
251253
- name: Use WebAssembly System Interface (WASI) node pools
252254
href: use-wasi-node-pools.md
253255
- name: Start/stop node pools

articles/aks/api-server-authorized-ip-ranges.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ The *API server authorized IP ranges* feature has the following limitations:
2626

2727
- 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.
2828
- 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.
3030

3131
## Overview of API server authorized IP ranges
3232

articles/aks/use-node-public-ips.md

Lines changed: 74 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -56,15 +56,33 @@ Finally, when creating a new cluster or adding a new node pool, use the flag `no
5656
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
5757
```
5858

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+
5974
## Use public IP tags on node public IPs (PREVIEW)
6075

6176
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.
6277

6378
[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
6479

65-
### Install the aks-preview Azure CLI extension
80+
### Requirements
6681

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
6886

6987
To install the aks-preview extension, run the following command:
7088

@@ -114,22 +132,7 @@ az aks nodepool add --cluster-name <clusterName> -n <nodepoolName> -l <location>
114132
--node-public-ip-tags RoutingPreference=Internet
115133
```
116134

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)
133136

134137
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.
135138

@@ -295,6 +298,7 @@ spec:
295298
```
296299
297300
When the deployment is applied, the `hostPort` entries will be in the YAML of the individual pods:
301+
298302
```shell
299303
$ kubectl describe pod echoserver-hostport-75dc8d8855-4gjfc
300304
<cut for brevity>
@@ -321,6 +325,57 @@ Containers:
321325

322326
<!-- EXTERNAL LINKS -->
323327

328+
[kubernetes-drain]: https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/
329+
[kubectl-get]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#get
330+
[kubectl-taint]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#taint
331+
[kubectl-describe]: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#describe
332+
[kubernetes-labels]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
333+
[kubernetes-label-syntax]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set
334+
[capacity-reservation-groups]:/azure/virtual-machines/capacity-reservation-associate-virtual-machine-scale-set
335+
324336
<!-- INTERNAL LINKS -->
337+
[arm-sku-vm1]: ../virtual-machines/dpsv5-dpdsv5-series.md
338+
[arm-sku-vm2]: ../virtual-machines/dplsv5-dpldsv5-series.md
339+
[arm-sku-vm3]: ../virtual-machines/epsv5-epdsv5-series.md
340+
[aks-quickstart-windows-cli]: ./learn/quick-windows-container-deploy-cli.md
341+
[az-aks-get-credentials]: /cli/azure/aks#az_aks_get_credentials
342+
[az-aks-create]: /cli/azure/aks#az_aks_create
343+
[az-aks-get-upgrades]: /cli/azure/aks#az_aks_get_upgrades
344+
[az-aks-nodepool-add]: /cli/azure/aks/nodepool#az_aks_nodepool_add
345+
[az-aks-nodepool-list]: /cli/azure/aks/nodepool#az_aks_nodepool_list
346+
[az-aks-nodepool-update]: /cli/azure/aks/nodepool#az_aks_nodepool_update
347+
[az-aks-nodepool-upgrade]: /cli/azure/aks/nodepool#az_aks_nodepool_upgrade
348+
[az-aks-nodepool-scale]: /cli/azure/aks/nodepool#az_aks_nodepool_scale
349+
[az-aks-nodepool-delete]: /cli/azure/aks/nodepool#az_aks_nodepool_delete
350+
[az-aks-show]: /cli/azure/aks#az_aks_show
351+
[az-extension-add]: /cli/azure/extension#az_extension_add
352+
[az-extension-update]: /cli/azure/extension#az_extension_update
325353
[az-feature-register]: /cli/azure/feature#az_feature_register
326-
[az-feature-list]: /cli/azure/feature#az_feature_list
354+
[az-feature-list]: /cli/azure/feature#az_feature_list
355+
[az-provider-register]: /cli/azure/provider#az_provider_register
356+
[az-group-create]: /cli/azure/group#az_group_create
357+
[az-group-delete]: /cli/azure/group#az_group_delete
358+
[az-deployment-group-create]: /cli/azure/deployment/group#az_deployment_group_create
359+
[az-aks-nodepool-add]: /cli/azure/aks#az_aks_nodepool_add
360+
[enable-fips-nodes]: enable-fips-nodes.md
361+
[gpu-cluster]: gpu-cluster.md
362+
[install-azure-cli]: /cli/azure/install-azure-cli
363+
[operator-best-practices-advanced-scheduler]: operator-best-practices-advanced-scheduler.md
364+
[quotas-skus-regions]: quotas-skus-regions.md
365+
[supported-versions]: supported-kubernetes-versions.md
366+
[tag-limitation]: ../azure-resource-manager/management/tag-resources.md
367+
[taints-tolerations]: operator-best-practices-advanced-scheduler.md#provide-dedicated-nodes-using-taints-and-tolerations
368+
[vm-sizes]: ../virtual-machines/sizes.md
369+
[use-system-pool]: use-system-pools.md
370+
[node-resource-group]: faq.md#why-are-two-resource-groups-created-with-aks
371+
[vmss-commands]: ../virtual-machine-scale-sets/virtual-machine-scale-sets-networking.md#public-ipv4-per-virtual-machine
372+
[az-list-ips]: /cli/azure/vmss#az_vmss_list_instance_public_ips
373+
[reduce-latency-ppg]: reduce-latency-ppg.md
374+
[public-ip-prefix-benefits]: ../virtual-network/ip-services/public-ip-address-prefix.md
375+
[az-public-ip-prefix-create]: /cli/azure/network/public-ip/prefix#az_network_public_ip_prefix_create
376+
[node-image-upgrade]: node-image-upgrade.md
377+
[use-tags]: use-tags.md
378+
[use-labels]: use-labels.md
379+
[cordon-and-drain]: resize-node-pool.md#cordon-the-existing-nodes
380+
[internal-lb-different-subnet]: internal-lb.md#specify-a-different-subnet
381+
[drain-nodes]: resize-node-pool.md#drain-the-existing-nodes

0 commit comments

Comments
 (0)