Skip to content

Commit ea09a2b

Browse files
Merge pull request #15867 from sethmanheim/vmsys
Fix VMWare PM submissions
2 parents 2bcbf37 + 63b924d commit ea09a2b

File tree

1 file changed

+10
-7
lines changed

1 file changed

+10
-7
lines changed

AKS-Hybrid/aks-vmware-system-requirements.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: System requirements and support matrix for AKS enabled by Azure Arc on VMware (preview)
33
description: Learn about system requirements and the support matrix for AKS enabled by Azure Arc on VMware.
4-
ms.date: 03/22/2024
4+
ms.date: 09/16/2024
55
ms.topic: conceptual
66
author: sethmanheim
77
ms.author: sethm
88
ms.reviewer: leslielin
9-
ms.lastreviewed: 03/22/2024
9+
ms.lastreviewed: 09/16/2024
1010

1111
ms.custom: references_regions
1212

@@ -74,24 +74,27 @@ In this preview release, you can only deploy the same Kubernetes version that th
7474

7575
## Custom location
7676

77-
If you choose to **Enable Kubernetes Service on VMware [preview]** when you **Connect vCenter to Azure** [from the Azure portal](/azure/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script), a custom location with the prefix **AKS-**, and a default namespace, are created for you to deploy AKS on VMware. If you **Enable Kubernetes Service on VMware [preview]** using the [Azure CLI process](aks-vmware-install-kubernetes-extension.md), you can specify the name of the custom location of your choice with the default namespace.
77+
If you choose to **Enable Kubernetes Service on VMware [preview]** when you **Connect vCenter to Azure** [from the Azure portal](/azure/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script), a custom location with the prefix **AKS-**, and a default namespace, are created for you to deploy AKS on VMware. If you enable the Azure Kubernetes Service on VMware using the [Azure CLI process](aks-vmware-install-kubernetes-extension.md), you can specify the name of the custom location of your choice with the default namespace.
7878

7979
> [!IMPORTANT]
8080
> You must use the **default** namespace.
8181
82-
To view the custom location namespace, use the `az customlocation show` command
82+
To view the custom location namespace, use the `az customlocation show` command:
83+
8384
```azurecli
8485
az customlocation show -g $customLocationResourceGroupName -n $customLocationName
8586
```
8687

87-
If your custom location was not created with the **default** namespace, use the following command to delete the custom location and create a custom location with the default namespace. To learn more about how to manage custom location, see [Create and manage custom locations](/azure/azure-arc/kubernetes/custom-locations)
88+
If your custom location was not created with the **default** namespace, use the following command to delete the custom location and create a custom location with the default namespace. For more information about how to manage custom locations, see [Create and manage custom locations](/azure/azure-arc/kubernetes/custom-locations).
89+
90+
Delete the custom location:
8891

89-
Delete the custom location
9092
```azurecli
9193
az customlocation delete -g $customLocationResourceGroupName -n $customLocationName
9294
```
9395

94-
Create the custom location with the **default** namespace
96+
Create the custom location with the **default** namespace:
97+
9598
```azurecli
9699
az customlocation create -g $customLocationResourceGroupName -n $customLocationName --cluster-extension-ids $clusteraksExtensionId --host-resource-id $ArcApplianceResourceId --namespace "default"
97100
```

0 commit comments

Comments
 (0)