Merge pull request #248081 from dramasamy/sku

Add Nexus AKS SKUs

Author: v-dirichards

articles/operator-nexus/TOC.yml

@@ -155,3 +155,5 @@
       href: reference-near-edge-storage.md
     - name: Limits & quotas
       href: reference-limits-and-quotas.md
+    - name: Nexus Kubernetes service VM SKUs
+      href: reference-nexus-kubernetes-cluster-sku.md

articles/operator-nexus/concepts-nexus-kubernetes-cluster.md

@@ -25,8 +25,7 @@ to learn about Kubernetes.
 
 ## Nexus Kubernetes cluster
 
-Nexus Kubernetes cluster (NKS) is an Operator Nexus version of Kubernetes for on-premises use. It is optimized to automate creation of containers to
-run tenant network function workloads.
+Nexus Kubernetes cluster (NKS) is an Operator Nexus version of Kubernetes for on-premises use. It is optimized to automate creation of containers to run tenant network function workloads.
 
 Like any Kubernetes cluster, Nexus Kubernetes cluster has two
 components:

articles/operator-nexus/includes/kubernetes-cluster/quickstart-arm-add-node-pool.json

@@ -58,7 +58,7 @@
       },
       "agentVmSku": {
         "type": "string",
-        "defaultValue": "NC_M4_v1",
+        "defaultValue": "NC_P10_56_v1",
         "metadata": {
           "description": "VM size of the agent nodes"
         }

articles/operator-nexus/includes/kubernetes-cluster/quickstart-arm-deploy.json

@@ -208,7 +208,7 @@
         "metadata": {
           "description": "The size of the control plane nodes"
         },
-        "defaultValue": "NC_G2_v1"
+        "defaultValue": "NC_G6_28_v1"
       },
       "systemPoolNodeCount": {
         "type": "int",
@@ -222,7 +222,7 @@
         "metadata": {
           "description": "The size of the worker nodes"
         },
-        "defaultValue": "NC_M4_v1"
+        "defaultValue": "NC_P10_56_v1"
       },
       "initialPoolAgentOptions": {
         "type": "object",

articles/operator-nexus/includes/kubernetes-cluster/quickstart-bicep-add-node-pool.bicep

@@ -25,7 +25,7 @@ param agentPoolNodeCount int = 1
 param agentPoolName string = 'nodepool-2'
 
 @description('VM size of the agent nodes')
-param agentVmSku string = 'NC_M4_v1'
+param agentVmSku string = 'NC_P10_56_v1'
 
 @description('The zones/racks used for placement of the agent pool nodes')
 param agentPoolZones array = []

articles/operator-nexus/includes/kubernetes-cluster/quickstart-bicep-deploy.bicep

@@ -107,13 +107,13 @@ param agentPoolZones array = []
 // "string" Example: ["1", "2", "3"]
 
 @description('The size of the control plane nodes')
-param controlPlaneVmSkuName string = 'NC_G2_v1'
+param controlPlaneVmSkuName string = 'NC_G6_28_v1'
 
 @description('The number of worker nodes to be deployed in the initial agent pool')
 param systemPoolNodeCount int = 1
 
 @description('The size of the worker nodes')
-param workerVmSkuName string = 'NC_M4_v1'
+param workerVmSkuName string = 'NC_P10_56_v1'
 
 @description('The configurations for the initial agent pool')
 param initialPoolAgentOptions object = {}

articles/operator-nexus/includes/kubernetes-cluster/quickstart-prereq.md

@@ -14,7 +14,9 @@ ms.custom: devx-track-azurecli
 * Install the latest version of the [necessary Azure CLI extensions](../../howto-install-cli-extensions.md).
 * This article requires version 2.49.0 or later of the Azure CLI. If using Azure Cloud Shell, the latest version is already installed.
 * If you have multiple Azure subscriptions, select the appropriate subscription ID in which the resources should be billed using the [`az account`][az-account] command.
+* Refer the VM SKU table in the [reference section](../../reference-nexus-kubernetes-cluster-sku.md) for the list of supported VM SKUs.
 * Create a resource group using the [`az group create`][az-group-create] command. An [Azure resource group][azure-resource-group] is a logical group in which Azure resources are deployed and managed. When you create a resource group, you're prompted to specify a location. This location is the storage location of your resource group metadata and where your resources run in Azure if you don't specify another region during resource creation. The following example creates a resource group named *myResourceGroup* in the *eastus* location.
+
     ```azurecli-interactive
     az group create --name myResourceGroup --location eastus
     ```
@@ -33,6 +35,7 @@ ms.custom: devx-track-azurecli
       "tags": null
     }
     ```
+
 * To deploy a Bicep file or ARM template, you need write access on the resources you're deploying and access to all operations on the Microsoft.Resources/deployments resource type. For example, to deploy a cluster, you need Microsoft.NetworkCloud/kubernetesclusters/write and Microsoft.Resources/deployments/* permissions. For a list of roles and permissions, see [Azure built-in roles](../../../role-based-access-control/built-in-roles.md).
 * You need the `custom location` resource ID of your Azure Operator Nexus cluster.
 * You need to create [various networks](../../quickstarts-tenant-workload-prerequisites.md#create-networks-for-tenant-workloads) according to your specific workload requirements, and it's essential to have the appropriate IP addresses available for your workloads. To ensure a smooth implementation, it's advisable to consult the relevant support teams for assistance.
@@ -42,5 +45,4 @@ ms.custom: devx-track-azurecli
 [kubernetes-concepts]: ../../../aks/concepts-clusters-workloads.md
 [az-account]: /cli/azure/account
 [az-group-create]: /cli/azure/group#az-group-create
-[az-group-delete]: /cli/azure/group#az-group-delete
 [azure-resource-group]: ../../../azure-resource-manager/management/overview.md

articles/operator-nexus/includes/kubernetes-cluster/quickstart-review-nodepool.md

@@ -16,6 +16,6 @@ $ az networkcloud kubernetescluster agentpool list --kubernetes-cluster-name myN
 This command is experimental and under development. Reference and support levels: https://aka.ms/CLI_refstatus
 Count    Location    Mode    Name                          ProvisioningState    ResourceGroup    VmSkuName
 -------  ----------  ------  ----------------------------  -------------------  ---------------  -----------
-1        eastus      System  myNexusAKSCluster-nodepool-1  Succeeded            myResourceGroup  NC_M4_v1
-1        eastus      User    myNexusAKSCluster-nodepool-2  Succeeded            myResourceGroup  NC_M4_v1
-```
+1        eastus      System  myNexusAKSCluster-nodepool-1  Succeeded            myResourceGroup  NC_P10_56_v1
+1        eastus      User    myNexusAKSCluster-nodepool-2  Succeeded            myResourceGroup  NC_P10_56_v1
+```

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-cli.md

@@ -62,10 +62,10 @@ K8S_VERSION="v1.24.9"
 ADMIN_USERNAME="azureuser"
 SSH_PUBLIC_KEY="$(cat ~/.ssh/id_rsa.pub)"
 CONTROL_PLANE_COUNT="1"
-CONTROL_PLANE_VM_SIZE="NC_G2_v1"
+CONTROL_PLANE_VM_SIZE="NC_G6_28_v1"
 INITIAL_AGENT_POOL_NAME="${CLUSTER_NAME}-nodepool-1"
 INITIAL_AGENT_POOL_COUNT="1"
-INITIAL_AGENT_POOL_VM_SIZE="NC_M4_v1"
+INITIAL_AGENT_POOL_VM_SIZE="NC_P10_56_v1"
 POD_CIDR="10.244.0.0/16"
 SERVICE_CIDR="10.96.0.0/16"
 DNS_SERVICE_IP="10.96.0.10"
@@ -120,7 +120,7 @@ RESOURCE_GROUP="myResourceGroup"
 CUSTOM_LOCATION="/subscriptions/<subscription_id>/resourceGroups/<managed_resource_group>/providers/microsoft.extendedlocation/customlocations/<custom-location-name>"
 CLUSTER_NAME="myNexusAKSCluster"
 AGENT_POOL_NAME="${CLUSTER_NAME}-nodepool-2"
-AGENT_POOL_VM_SIZE="NC_M4_v1"
+AGENT_POOL_VM_SIZE="NC_P10_56_v1"
 AGENT_POOL_COUNT="1"
 AGENT_POOL_MODE="User"
 ```

articles/operator-nexus/reference-nexus-kubernetes-cluster-sku.md

@@ -0,0 +1,53 @@
+---
+title: Azure Operator Nexus Kubernetes cluster VM SKUs
+description: Learn about Azure Operator Nexus Kubernetes cluster SKUs
+author: dramasamy
+ms.author: dramasamy
+ms.service: azure-operator-nexus
+ms.topic: reference
+ms.date: 08/11/2023
+ms.custom: template-reference
+---
+
+# Azure Operator Nexus Kubernetes cluster VM SKUs
+
+The Azure Operator Nexus Kubernetes cluster VMs are grouped into node pools, which are collections of VMs that have the same configuration. The VMs in a node pool are used to run your Kubernetes workloads. The Azure Operator Nexus Kubernetes cluster supports the following VM SKUs. These SKUs are available in all Azure regions where the Azure Operator Nexus Kubernetes cluster is available.
+
+There are two types of VM SKUs:
+
+* General purpose
+* Performance optimized
+
+The primary difference between the two types of VMs is their approach to emulator thread isolation. VM SKUs optimized for performance have dedicated emulator threads, which allow each VM to operate at maximum efficiency. Conversely, general-purpose VM SKUs have emulator threads that run on the same processors as applications running inside the VM. For application workloads that cannot tolerate other workloads sharing their processors, we recommend using the performance-optimized SKUs.
+
+All these SKUs are having the following characteristics:
+
+- Dedicated host-to-VM CPU mapping
+- Reserved CPUs for Kubelet are 0 and 1, except for NC_G2_8_v1 and NC_P4_28_v1
+
+These VM SKUs can be used for both worker and control plane nodes within the Azure Operator Nexus Kubernetes cluster.
+
+## General purpose VM SKUs
+
+| VM SKU Name   | vCPU | Memory (GiB) | Root Disk (GiB) |
+|---------------|----------------|------------|------------------|
+| NC_G48_224_v1 | 48             | 224        | 300              |
+| NC_G36_168_v1 | 36             | 168        | 300              |
+| NC_G24_112_v1 | 24             | 112        | 300              |
+| NC_G12_56_v1  | 12             | 56         | 300              |
+| NC_G6_28_v1   | 6              | 28         | 300              |
+| NC_G2_8_v1    | 2              | 8          | 300              |
+
+## Performance optimized VM SKUs
+
+| VM SKU Name   | vCPU | Memory (GiB) | Root Disk (GiB) |
+|---------------|----------------|------------|------------------|
+| NC_P46_224_v1 | 46             | 224        | 300              |
+| NC_P34_168_v1 | 34             | 168        | 300              |
+| NC_P22_112_v1 | 22             | 112        | 300              |
+| NC_P10_56_v1  | 10             | 56         | 300              |
+| NC_P4_28_v1   | 4              | 28         | 300              |
+
+## Next steps
+
+Try these SKUs in the Azure Operator Nexus Kubernetes cluster. For more information, see [Quickstart: Deploy an Azure Operator Nexus Kubernetes cluster](./quickstarts-kubernetes-cluster-deployment-bicep.md).