-
Notifications
You must be signed in to change notification settings - Fork 581
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
When using an s3 bucket, add a vpc endpoint #4577
Conversation
/test pull-cluster-api-provider-aws-e2e |
/test pull-cluster-api-provider-aws-e2e |
b5a8386
to
9b5cd66
Compare
/retest |
/test pull-cluster-api-provider-aws-e2e |
@richardcase wdyt of the release note? |
92480c8
to
16d3851
Compare
/test pull-cluster-api-provider-aws-build |
/test pull-cluster-api-provider-aws-e2e |
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.
Can we please describe in code (function docs for reconcileVPCEndpoints
) and this PR why exactly this is helpful, required, etc.? Maybe link to https://docs.aws.amazon.com/vpc/latest/privatelink/vpc-endpoints-s3.html. Is this a difference in pricing? I guess requests then don't require a NAT/internet gateway anymore? The benefits should be substantial since we need quite a few new permissions.
31637f8
to
7d416aa
Compare
/test pull-cluster-api-provider-aws-e2e |
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.
I'm okay with the change, but the tests are currently failing.
pkg/cloud/services/network/vpc.go
Outdated
Values: []*string{&vpc.ID}, | ||
}), | ||
} | ||
// Create a map of existing endpoints. |
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.
[minor]
This comment seems outdated. You're returning a slice.
@AndiDog comments have been addressed, ptal |
/lgtm |
/test pull-cluster-api-provider-aws-e2e |
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.
This looks good to me, thanks @vincepri . Lets get the e2e passing and then i think we are good to go on this.
@vincepri: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
Signed-off-by: Vince Prignano <[email protected]>
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
@vincepri E2E tests are continuously failing after this PR merge, please either fix the test or revert the change. |
What type of PR is this?
What this PR does / why we need it:
/kind feature
Attach the routing tables to an s3 regional vpc endpoint.
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 #
Special notes for your reviewer:
Checklist:
Release note: