6.3.2. Deploy Node Pool for Targets

Targets are deployed using a node pool.
They can be either in one availability zone or across two.
A PPG (proximity placement group) is needed per AZ (availability zone) used.

To create the PPG, use:

az ppg create -n <ppgName> -g <resourceGroupName> -l <region> -t standard

Then deploy a node pool per AZ with the PPG id returned from the previous command, as follows:

az aks nodepool add --resource-group myResourceGroup --cluster-name myAKSCluster --name <nodepool name> --node-vm-size Standard_L48s_v2 --node-count <node-count> --ppg <myPPGResourceID> --labels nvmesh.excelero.com/nvmesh-management="" nvmesh.excelero.com/nvmesh-client="" nvmesh.excelero.com/nvmesh-target="" --zones <zone-id>

The node count should be 4 for a single AZ.
For cross-AZ, the node count should be 2 for each AZ. To ensure failover, add to the node pool another node of any type that will be used as an arbiter. Contact Excelero Technical Support for more in-depth instructions for ensuring failover.

For more storage, simply add additional node pools.

To know in which zones there are nodes of this type, use:

az vm list-skus -l eastus2 --zone --size "Standard_L48s_v2"

This will provide a response, see the following example excerpt, that lists the zones where the nodes are available.

  "locationInfo": [
     {
       "location": "eastus2",
       "zoneDetails": [
         {
           "Name": [
             "3",
             "2",
             "1"
           ],
           "capabilities": [
             {
               "name": "UltraSSDAvailable",
               "value": "True"
             }
           ],
           "name": null
         }
       ],
       "zones": [
         "3",
         "2",
         "1"
       ]
     }
   ],
   "locations": [
     "eastus2"
   ],
   "name": "Standard_L48s_v2",
   "resourceType": "virtualMachines",
   "restrictions": [],
   "size": "L48s_v2",
   "tier": "Standard"