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

AWS PrivateLink: "Spread" VPC endpoints across VPCs #1744

Merged

Conversation

2uasimojo
Copy link
Member

@2uasimojo 2uasimojo commented Apr 11, 2022

Since we don't know the actual quota of endpoints per VPC, remove the arbitrary limit check, and create new endpoints in the least-used VPC. The result should be that we hit quota only when all the VPCs are full.

HIVE-1803

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 11, 2022
@2uasimojo
Copy link
Member Author

2uasimojo commented Apr 11, 2022

Working on UT.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 11, 2022
@codecov
Copy link

codecov bot commented Apr 11, 2022

Codecov Report

Merging #1744 (875d3ac) into master (5ccea30) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1744      +/-   ##
==========================================
- Coverage   41.76%   41.74%   -0.03%     
==========================================
  Files         346      346              
  Lines       32118    32106      -12     
==========================================
- Hits        13415    13403      -12     
  Misses      17583    17583              
  Partials     1120     1120              
Impacted Files Coverage Δ
...roller/awsprivatelink/awsprivatelink_controller.go 66.38% <100.00%> (-0.12%) ⬇️
pkg/controller/awsprivatelink/vpcinventory.go 84.21% <100.00%> (-2.16%) ⬇️

Since we don't know the actual quota of endpoints per VPC, create new
endpoints in the least-used VPC. The result should be that we hit quota
only when all the VPCs are full.

HIVE-1803
We had logic to filter out VPCs based on a hardcoded maximum number of
allowed endpoints. That limit is actually based on a (changeable) quota
set by AWS. In the future we may attempt to discover that quota and
reinstate the filter; but for now simply remove it.

HIVE-1803
Fix some yellow squiggly lines in VSCode.
@2uasimojo
Copy link
Member Author

/assign @abutcher

@2uasimojo 2uasimojo changed the title WIP: AWS PrivateLink: "Spread" VPC endpoints across VPCs AWS PrivateLink: "Spread" VPC endpoints across VPCs Apr 12, 2022
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 12, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 12, 2022

@2uasimojo: all tests passed!

Full PR test history. Your PR dashboard.

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.

@abutcher
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 13, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 13, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 2uasimojo, abutcher

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 4dc9b80 into openshift:master Apr 13, 2022
@2uasimojo 2uasimojo deleted the HIVE-1803/vpc-limits branch April 13, 2022 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants