Prerequest document update request

[n-y-kim]

Hi, I was trying this pre-configured AKS construction setting, and it was throwing error like this:

The VM size of Standard_B4ms is not allowed in your subscription in location 'eastus2'. 
The available VM sizes are 
'standard_d11,standard_d12,standard_d13,standard_d14,standard_d16lds_v5,standard_d16ls_v5,standard_d16pds_v5,standard_d16plds_v5,standard_d16pls_v5,standard_d16ps_v5,standard_d2,standard_d2lds_v5,standard_d2ls_v5,standard_d2pds_v5,standard_d2plds_v5,standard_d2pls_v5,standard_d2ps_v5,standard_d3,standard_d32lds_v5,standard_d32ls_v5,standard_d32pds_v5,standard_d32plds_v5,standard_d32pls_v5,standard_d32ps_v5,standard_d4,standard_d48lds_v5,standard_d48ls_v5,standard_d48pds_v5,standard_d48plds_v5,standard_d48pls_v5,standard_d48ps_v5,standard_d4lds_v5,standard_d4ls_v5,standard_d4pds_v5,standard_d4plds_v5,standard_d4pls_v5,standard_d4ps_v5,standard_d64lds_v5,standard_d64ls_v5,standard_d64pds_v5,standard_d64plds_v5,standard_d64pls_v5,standard_d64ps_v5,standard_d8lds_v5,standard_d8ls_v5,standard_d8pds_v5,standard_d8plds_v5,standard_d8pls_v5,standard_d8ps_v5,standard_d96lds_v5,standard_d96ls_v5,standard_dc16ds_v3,standard_dc16s_v3,standard_dc24ds_v3,standard_dc24s_v3,standard_dc2as_v5,standard_dc2ds_v3,standard_dc2s_v3,standard_dc32ds_v3,standard_dc32s_v3,standard_dc48ds_v3,standard_dc48s_v3,standard_dc4ds_v3,standard_dc4s_v3,standard_dc8ds_v3,standard_dc8s_v3,standard_ds11,standard_ds12,standard_ds13,standard_ds14,standard_ds2,standard_ds3,standard_ds4,standard_e112iads_v5,standard_e112ias_v5,standard_e16pds_v5,standard_e16ps_v5,standard_e20pds_v5,standard_e20ps_v5,standard_e2pds_v5,standard_e2ps_v5,standard_e32pds_v5,standard_e32ps_v5,standard_e4pds_v5,standard_e4ps_v5,standard_e8pds_v5,standard_e8ps_v5,standard_ec8ads_v5,standard_nc24ads_a100_v4,standard_nc48ads_a100_v4,standard_nc96ads_a100_v4,standard_nv12s_v2,standard_nv24s_v2,standard_nv6s_v2' 

At first, I thought there were problems with main.json or the configuration of the AKS clusters. But after going through multiple deployments & cleaning ups, it was just my Microsoft internal subscription, which had limits with multiple VM sizes. I needed to look up main.js's default VM skus and match them with my available VM sku.

And I thought this wouldn't be just my problem for those who are trying to walk through the CI/CD demo for AKS.

What I wanted to suggest is, maybe writing extra instructions at the prerequest README such as:

Please check available skus for VMs using these commands before deploying the auto-generated construction commands. (And maybe list up the VM skus used in main.json so that the users do not have to look them up by themselves, and focus on the demo itself)

(bash) az vm list-skus --location eastus2 -o table

would definitely help others who stumble upon the same problem as me. (Especially MS internally, as MCAPS subscription seems to have a lot of restrictions)