-
Notifications
You must be signed in to change notification settings - Fork 40k
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
AWS Cloud Provider Cleanup #14879
AWS Cloud Provider Cleanup #14879
Conversation
Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist") If this message is too spammy, please complain to ixdy. |
cc @justinsb |
Labelling this PR as size/L |
@justinsb: Any feedback on these changes? |
Hi - @tpounds sorry for the delay and thanks for these fixes! These look good, though I think 9c59dc707d32f38b2a89c5274424466cb84508ac would benefit from being its own PR, as I'm less certain about it. The others are all self-evident improvements, so without 9c59dc707 it would be an easy LGTM. |
@justinsb: Thanks for the feedback! I'll cherry-pick 9c59dc7 into a separate pull request and we can discuss the merits or lack there of elsewhere. :) |
The external DescribeVPCs call is unnecessary since only the VPC ID is used and it is retrieved from the EC2 metadata service.
The availability zone always exist since it is retrieved from the instance's EC2 metadata service during cloud provider construction.
Labelling this PR as size/M |
Thanks for making this one easier by separating that one commit! LGTM. |
@k8s-bot ok to test
|
GCE e2e test build/test passed for commit 5d5013a. |
The author of this PR is not in the whitelist for merge, can one of the admins add the 'ok-to-merge' label? |
This is just some minor cleanup now that the new AWS SDK has been merged. It contains the following two changes: