-
Notifications
You must be signed in to change notification settings - Fork 431
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
Use MSI ClientID as userAssignedIdentityID in azure.json #2214
Conversation
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.
/assign @jackfrancis
I would really like to validate |
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.
looks good overall with a couple of nits.
165b664
to
10d5f93
Compare
/test pull-cluster-api-provider-azure-e2e-optional |
Updated to validate user-assigned identity in the existing external-cloud-provider and dual-stack (internal cloud-provider) test specs. This requires a user-assigned identity to exist before running tests, as described in the comments in azure_test.go. This is already true for the CI subscription. |
/test pull-cluster-api-provider-azure-e2e-optional |
/retest |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherry-pick release-1.3 @mboersma thoughts on cutting a release to include this one? |
@CecileRobertMichon: new pull request created: #2309 In response to this:
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. |
Yes, I think we should, otherwise user-assigned ID stays broken for most users. |
patch patch ♻️ cleanup patch 📝 linter fix make
patch patch ♻️ cleanup patch 📝 linter fix make conflict fix
patch patch ♻️ cleanup patch 📝 linter fix make conflict fix conflict fix
patch patch ♻️ cleanup patch 📝 linter fix make conflict fix conflict fix
…sigs#2214" This reverts commit 48768e4.
…sigs#2214" This reverts commit 48768e4.
Revert "⏪ reverted userAssignedIdenties logic based on PR #2214"
…sigs#2214" This reverts commit 48768e4.
…4064-to-release-1.11 [release-1.11] Revert "⏪ reverted userAssignedIdenties logic based on PR #2214"
What type of PR is this?
/kind bug
What this PR does / why we need it:
Uses a lookup function to translate providerID to ClientID when creating
azure.json
on nodes.Which issue(s) this PR fixes:
Fixes #2164
Special notes for your reviewer:
This is a hack and I'm open for suggestions as to how to make it conform better with our service and reconciler models. Also, it needs regression tests to ensure
azure.json
doesn't revert. (I've tested this interactively.)TODOs:
Release note: