Missing defaults
See original GitHub issueHi team
I have a customer asking about the default values for the az aks create
command.
The parameters they’re interested in are:
--vm-set-type
--zones
Our documentation is missing defaults for many available options. Can this be resolved?
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: d75c3a8d-1187-bea1-a7d4-7ebba71c1790
- Version Independent ID: 75b0c352-762e-16ae-5cc6-d807ffc1dc3f
- Content: az aks
- Content Source: latest/docs-ref-autogen/aks.yml
- Service: container-service
- GitHub Login: @rloutlaw
- Microsoft Alias: routlaw
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
The Curious Case of the Missing Defaults - Publications
In a recent paper on the long coincident behavior of international capital flows, commodity prices, and interest rates in global financial centers, my...
Read more >What does warning: type specifier missing, defaults to 'int ...
The compiler warning tells you that you did not specify a type for the return value of your main() function. Because of that...
Read more >hello_world_c: warning: type specifier missing, defaults to 'int ...
This warning is shown when the hello_world_c project is built: warning: type specifier missing, defaults to 'int' [-Wimplicit-int] It seems ...
Read more >10 Required args shouldn't have defaults
A common warning sign is the use of missing() inside the function. 10.3 What are the exceptions? There are two exceptions to this...
Read more >South Dakota Missing Persons
South Dakota Missing Persons. If you have investigative information on a missing person please call the reporting law enforcement agency listed.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found some answers myself in the documentation of our REST api:
https://docs.microsoft.com/en-us/rest/api/aks/managed-clusters/create-or-update#agentpooltype
https://docs.microsoft.com/en-us/rest/api/aks/managed-clusters/create-or-update#managedclusteragentpoolprofile
The list of Availability zones to use for nodes. This can only be specified if the AgentPoolType property is 'VirtualMachineScaleSets'.
Thanks @RakeshMohanMSFT
Hopefully we can get more insights on that, because --vm-set-type is a choice of two options, and one of them will be chosen if not provided, I’d assume the newer VMSS would be chosen. Same with --zones, when a VMSS option is used, zones have to be provided so something is making a default selection somewhere.
Not sure why our documentation is unclear about this.