--node-osdisk-size in CLI is configured to use GB whereas the VMsizes are using GiB which is creating confusion.

[anilkumar1619]

[###]([url](u Describe the bug

Hello Team,

This is regarding "--node-osdisk-size" parameter in the az aks nodepool add command, which is configured to use the disk measurements in GB whereas the VM SKUs are configured to use GiB which is creating confusion.

Default disk size measurements for the VM SKUs are mentioned in GiB but "--node-osdisk-size" is creating disk with GB which is creating a confusion because customer is looking to create nodepool with 128Gib disk size but it is creating with less size as the parameters are defined to use GB. Nodepool or VMSS disk size measurement is defined in GiB but this parameters are using GB which is confusing customers. Please do the needful. Please confirm if this is expected.

Related command

az aks nodepool add -h

Errors

No error.

Issue script & Debug output

NA

Expected behavior

NA

Environment Summary

NA

Additional context

NA

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dyu1208, @FumingZhang, @andyliuliming.

[anilkumar1619]

Hello Team, @dyu1208 @FumingZhang @andyliuliming. Kindly assist.

[FumingZhang]

@anilkumar1619, thanks for the feedback, fixing the issue in PR #27592

[anilkumar1619]

@FumingZhang Thank you for the response. Any ETA on the fix.

[FumingZhang]

The upcoming azure-cli release is on 11/15