-
Notifications
You must be signed in to change notification settings - Fork 3.3k
WIP [AKS] az aks create: add enable-encryption-at-host parameter #17130
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
Conversation
|
@fengzhou-msft @yungezz do you know how to trigger the CI tests? thanks. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 17130 in repo Azure/azure-cli |
|
@kairu-ms could you help run test again? thanks. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
3a96f6c to
b2d5908
Compare
|
would you trigger test again? thanks. |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
would you trigger test again? thanks. |
|
/azp run |
|
Commenter does not have sufficient privileges for PR 17130 in repo Azure/azure-cli |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
hi @andyzhangx we'll enable permsision to trigger CI pipeline for you soon. Recently Azure CLI got attacked via CI so we temporarily disabled it before solution ready. Pls ping me or @fengzhou-msft for CI need for now. Sorry for inconvinience. :) |
|
@andyzhangx can you resolve the conflicts and take a look at the CI failures? This PR #17229 bumped API version to 2021-02-01. |
|
hi @andyzhangx could you pls rebase the PR? |
|
close this PR since EncryptionAtHost feature GA on AKS is postponed |
Description
This PR:
az aks createandaz aks nodepool addTesting 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 feature.
This 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.