-
Notifications
You must be signed in to change notification settings - Fork 415
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
update the container-service sdk from 2020-02-01 to 2021-03-01 #1416
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @LochanRn. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This is just an initial commit to review changes/modifications done after changing the containerservice sdk. |
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.
The update of the API version looks good. I only question the VMSizeTypes
to *string
change and what it means about the behavior of the PUT
request to Azure.
The change can be seen by comparing: API version 2021-02-01 and API version 2021-03-01.
One thing to consider. Perhaps, this should be it's own PR, rather than combining this with the AAD support as the name of the PR implies, [WIP] aad support for aks
.
@@ -52,7 +52,7 @@ func (s *Service) Reconcile(ctx context.Context, spec interface{}) error { | |||
|
|||
profile := containerservice.AgentPool{ | |||
ManagedClusterAgentPoolProfileProperties: &containerservice.ManagedClusterAgentPoolProfileProperties{ | |||
VMSize: containerservice.VMSizeTypes(agentPoolSpec.SKU), | |||
VMSize: &agentPoolSpec.SKU, |
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.
I think the enumeration of VMSizeTypes
was too restrictive and the AKS team wanted to allow any string to be specified regardless of the string being in the set of VMSizeTypes
.
@CecileRobertMichon what do you think?
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.
You’d be correct :)
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.
Thank you for the confirmation, @alexeldeib!
/ok-to-test |
@LochanRn please amend the commit to accurately describe what this is doing (it's not actually adding support for AAD) |
/test pull-cluster-api-provider-azure-e2e-windows |
I tried creating an aks cluster from this changeset, getting:
/hold |
@alexeldeib can you validate that setting the agent pool to mode System for now is appropriate to mitigate the error until #1376 is implemented? |
@LochanRn: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
…pi-provider-azure into aad-aks-support
@LochanRn: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
closing this PR as it is fixed in #1475 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Updates the existing containerService sdk to the latest version i.e 2021-03-01.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1418
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: