-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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] az aks nodepool upgrade
: Fix --node-soak-duration
cannot be set to 0
#30778
[AKS] az aks nodepool upgrade
: Fix --node-soak-duration
cannot be set to 0
#30778
Conversation
️✔️AzureCLI-FullTest
|
️✔️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>
|
Please update your PR title to follow the guidance. If you don't want to leave a history note in the release note, use |
az aks nodepool upgrade
: fix --node-soak-duration
cannot be set to 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
az aks nodepool upgrade
: fix --node-soak-duration
cannot be set to 0az aks nodepool upgrade
: Fix --node-soak-duration
cannot be set to 0
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Related command
az aks nodepool upgrade
Description
fix the issue that
az aks nodepool upgrade
cannot set node_soak_duration to 0Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a
: Make some customer-facing breaking change[Component Name 2]
az command b
: Add some customer-facing featureThis 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.