[AKS] Update network plugin defaults and long summary#31516
[AKS] Update network plugin defaults and long summary#31516zhoxing-ms merged 1 commit intoAzure:devfrom
Conversation
Signed-off-by: Sam Foo <samfoo@microsoft.com>
️✔️AzureCLI-FullTest
|
|
Hi @sf-msft, |
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull Request Overview
Updates the AKS help text for network plugin settings in az aks create to reflect that Azure CNI is now the default and to clarify mode behavior.
- Change
--network-pluginlong-summary to show default is now "azure" and adjust wording. - Revise
--network-plugin-modelong-summary to note default and pod IP assignment details.
| type: string | ||
| short-summary: The Kubernetes network plugin to use. | ||
| long-summary: Specify "azure" for routable pod IPs from VNET, "kubenet" for non-routable pod IPs with an overlay network, or "none" for no networking configured. Defaults to "kubenet". | ||
| long-summary: Specify "azure" for highly scalable networking, "kubenet" for IP assignment from subnet NAT-based routing, or "none" for no networking configured. Defaults to "azure". |
There was a problem hiding this comment.
[nitpick] The phrase "highly scalable networking" is vague in this context. Consider replacing it with a more descriptive explanation, for example: "Specify "azure" to use Azure CNI (pod IPs assigned directly from the VNet), "kubenet" for NAT-based routing from the subnet, or "none" for no networking. Defaults to "azure"."
| long-summary: Specify "azure" for highly scalable networking, "kubenet" for IP assignment from subnet NAT-based routing, or "none" for no networking configured. Defaults to "azure". | |
| long-summary: Specify "azure" to use Azure CNI (pod IPs assigned directly from the VNet), "kubenet" for NAT-based routing from the subnet, or "none" for no networking configured. Defaults to "azure". |
| Used to control the mode the network plugin should operate in. Defaults to "overlay". If not specified with "azure" as | ||
| network plugin, pods are given routable IPs from VNET. |
There was a problem hiding this comment.
This sentence is unclear and potentially inaccurate. --network-plugin-mode only applies to the Azure plugin; pods with the kubenet plugin always receive non-routable IPs through NAT. Consider clarifying: "Only applies when --network-plugin=azure. With azure, defaults to overlay mode (an overlay network); with kubenet, pods always use NAT-based routing."
| Used to control the mode the network plugin should operate in. Defaults to "overlay". If not specified with "azure" as | |
| network plugin, pods are given routable IPs from VNET. | |
| Only applies when `--network-plugin=azure`. Used to control the mode the network plugin should operate in. Defaults to "overlay" mode (an overlay network). | |
| With `--network-plugin=azure`, pods are given routable IPs from the VNET. With `--network-plugin=kubenet`, pods always use NAT-based routing and receive non-routable IPs. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Related command
az aks createDescription
xref: Azure/AKS#4897
Fixed help text inaccuracies with defaults and updated longer summary text to reflect current CNI options
Testing Guide
--network-pluginno longer defaults to kubenetHistory Notes
[AKS]
--network-plugin: Update longer summary to show "azure" is default instead of kubenetThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.