Skip to content

Commit 7457255

Browse files
committed
Updated connection options section based on customer feedback
1 parent 8e3f46e commit 7457255

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/aks/private-clusters.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
title: Create a private Azure Kubernetes Service (AKS) cluster
33
description: Learn how to create a private Azure Kubernetes Service (AKS) cluster
44
ms.topic: article
5+
ms.author: schaffererin
6+
author: schaffererin
57
ms.date: 06/29/2023
68
ms.custom: references_regions, devx-track-azurecli
79
---
@@ -211,6 +213,7 @@ The API server endpoint has no public IP address. To manage the API server, you'
211213
* Use an [Express Route or VPN][express-route-or-VPN] connection.
212214
* Use the [AKS `command invoke` feature][command-invoke].
213215
* Use a [private endpoint][private-endpoint-service] connection.
216+
* Use a [Cloud Shell][cloud-shell-vnet] instance deployed into a subnet that's connected to the API server for the cluster.
214217

215218
> [!NOTE]
216219
> Creating a VM in the same VNet as the AKS cluster is the easiest option. Express Route and VPNs add costs and require additional networking complexity. Virtual network peering requires you to plan your network CIDR ranges to ensure there are no overlapping ranges.
@@ -401,3 +404,4 @@ For associated best practices, see [Best practices for network connectivity and
401404
[az-network-vnet-peering-create]: /cli/azure/network/vnet/peering#az_network_vnet_peering_create
402405
[az-network-vnet-peering-list]: /cli/azure/network/vnet/peering#az_network_vnet_peering_list
403406
[intro-azure-linux]: ../azure-linux/intro-azure-linux.md
407+
[cloud-shell-vnet]: ../cloud-shell/vnet/overview.md

0 commit comments

Comments
 (0)