-
Notifications
You must be signed in to change notification settings - Fork 756
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 AWS VPC CNI to SDK V2 Update - master branch #3070
Conversation
3d25538
to
9af60b9
Compare
ef2146e
to
4490661
Compare
8f59421
to
8b83393
Compare
0914a5d
to
307a967
Compare
307a967
to
cd016a2
Compare
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
if errors.As(err, &awsErr) { | ||
log.Debugf("Insufficient IP Addresses due to: %v\n", awsErr.Code()) | ||
return awsErr.Code() == INSUFFICIENT_CIDR_BLOCKS || awsErr.Code() == INSUFFICIENT_FREE_IP_SUBNET | ||
if errors.As(err, &apiErr) { |
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.
we should test whether those error check is still true with sdkv2.
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 Error messages themselves are service errors, those remain true. SDK exposes them via interface like ErrorCode()
instead of Code()
. I had verified with OperationsError
. Relied in Integration tests for the others.
HTTPClient: &http.Client{ | ||
Timeout: getHTTPTimeout(), | ||
}, | ||
STSRegionalEndpoint: endpoints.RegionalSTSEndpoint, |
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.
How is the endpoints resolve option handled in the SDK v2:
STSRegionalEndpoint: endpoints.RegionalSTSEndpoint,
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.
^ In SDK v2, all sts interaction is regional only. It is transparently handled by SDK. This STSRegionalEndpoint: endpoints.RegionalSTSEndpoint, flag is not required andthe package endpoints is removed too.
This fixes the issue - #3116
Ensure Integration Tests are successful before merge.
Integration Tests on IPV4
Integration Tests on IPv6
CNI Metrics Helper