Skip to content
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

Merged
merged 17 commits into from
Dec 9, 2024
Merged

Conversation

orsenthil
Copy link
Member

@orsenthil orsenthil commented Oct 12, 2024

This fixes the issue - #3116

Ensure Integration Tests are successful before merge.

Integration Tests on IPV4

  • CNI

image

  • IPAMD

image

  • SNAT

image

  • Custom Networking

image

  • custom-networking-sgpp

image

  • ENI Subnet Discovery

image

  • pod-eni

image

Integration Tests on IPv6

  • IPv6

image

  • cni-egress on IPv6 Cluster

image

CNI Metrics Helper

  • Against the locally build image.

image

@orsenthil orsenthil requested a review from a team as a code owner October 12, 2024 01:48
@orsenthil orsenthil removed the request for review from a team October 15, 2024 23:38
@orsenthil orsenthil force-pushed the sdk_v2_update branch 3 times, most recently from 3d25538 to 9af60b9 Compare October 18, 2024 00:38
@orsenthil orsenthil changed the base branch from release-test-sdk-v2-update to master October 18, 2024 02:37
@orsenthil orsenthil force-pushed the sdk_v2_update branch 4 times, most recently from ef2146e to 4490661 Compare October 24, 2024 17:56
@orsenthil orsenthil changed the title [Work in Progress ] - SDK V2 Update [Ready for Review ] - SDK V2 Update Nov 29, 2024
@orsenthil orsenthil requested a review from a team December 3, 2024 23:18
@orsenthil orsenthil changed the title [Ready for Review ] - SDK V2 Update Update AWS VPC CNI to SDK V2 Update - master branch Dec 3, 2024
M00nF1sh
M00nF1sh previously approved these changes Dec 4, 2024
Copy link
Contributor

@M00nF1sh M00nF1sh left a 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) {
Copy link
Contributor

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.

Copy link
Member Author

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.

1. Fix an ipamd service for ipv6 cluster.
2. Use default when endpoint is not given.
@orsenthil orsenthil merged commit 8dd2a5a into master Dec 9, 2024
5 checks passed
@orsenthil orsenthil deleted the sdk_v2_update branch January 18, 2025 00:44
HTTPClient: &http.Client{
Timeout: getHTTPTimeout(),
},
STSRegionalEndpoint: endpoints.RegionalSTSEndpoint,
Copy link
Member Author

@orsenthil orsenthil Feb 7, 2025

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,

Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants