Add warning about aks-preview extension incompatibility with AKS Automatic BYO VNet - #444
Conversation
|
@pineapplethevoyager : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
@pineapplethevoyager : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Hi @pineapplethevoyager - This pull request was opened in the public repo. Microsoft contributors should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you! Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
Learn Build status updates of commit a815f00: ✅ Validation status: passed
For more details, please refer to the build report. |
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
Summary
Adds an IMPORTANT callout box to both AKS Automatic custom VNet quickstart docs (private and public) explaining that the
aks-previewCLI extension is incompatible with these deployments.Context
Since hosted system pool GA on June 2, 2026, the
aks-previewextension overrides theaz aks createcommand surface and hides the required--node-subnet-idand--system-node-subnet-idparameters. Customers who have the extension installed and fall back to the legacy--vnet-subnet-idparameter will have their deployment accepted by the RP but it will fail after up to 2 hours during node provisioning (NIC creation against a non-existent VNet).The existing prerequisite bullet says to uninstall the extension but does not explain the consequences of ignoring it. This PR adds a prominent warning callout that explains:
Related
articles/aks/automatic/quick-automatic-private-custom-network.mdarticles/aks/automatic/quick-automatic-custom-network.md