-
Notifications
You must be signed in to change notification settings - Fork 579
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
Zero csi driver aws credentials to fallback to use instance profile role #4262
Conversation
/test pull-cluster-api-provider-aws-e2e |
Nice |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Skarlso 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 |
Eh what the heck is jobs pages. |
Oh the job called Pages. Uuuh. |
It's still running 😨 |
Thanks @wyike, this helped solve the issue with E2E tests. |
Hahaha, that's fantastic. :D |
/cherry-pick release-2.1 |
@wyike: new pull request created: #4279 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. |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Based on #4250, we can zero csi driver aws credentials to fallback to use instance profile role, which is a more practical user scenario.
In addition, we need to pin csi controller deployment to control plane, which is explained in #4260 (comment).
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 #4260
Special notes for your reviewer:
Checklist:
Release note: