Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AKS Learn feedback: guidance needed on Node Autoprovisioning and Availability Zone support #123474

Open
seth-capistron opened this issue Jun 21, 2024 · 2 comments

Comments

@seth-capistron
Copy link

seth-capistron commented Jun 21, 2024

Type of issue

Missing information

Feedback

The AKS Node Autoprovisioning documentation needs guidance on how availability zones is (or is not) supported. For example, I created a cluster like so (note the --zones)...

az aks create --name $ClusterName --resource-group $ResourceGroupName --node-provisioning-mode Auto --network-plugin azure --network-plugin-mode overlay --network-dataplane cilium --generate-ssh-keys --zones 1 2 3

When node autoprovisioning began scaling out using the default node pool, it did not do so evenly across availability zones. I ended up with one node in Zone 1, one node in Zone 2, and seven nodes in Zone 3.

I'm expecting the documentation to be able to guide me to set up my cluster so nodes are evenly spread across zones, or call out in the limitations if that isn't supported.

Page URL

https://learn.microsoft.com/en-us/azure/aks/node-autoprovision?tabs=azure-cli

Content source URL

https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/aks/node-autoprovision.md

Author

@schaffererin

Document Id

95c14403-410d-7453-8407-eb4493788953


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@PesalaPavan
Copy link
Contributor

@seth-capistron
Thanks for your feedback! We will investigate and update as appropriate.

@AjayBathini-MSFT
Copy link
Contributor

@seth-capistron
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants
@seth-capistron @schaffererin @AjayBathini-MSFT @PesalaPavan and others