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

pull-cloud-provider-aws-e2e tests are failing due to limit issue - Requires limit increase #7467

Open
mmerkes opened this issue Oct 29, 2024 · 7 comments
Labels
sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.

Comments

@mmerkes
Copy link

mmerkes commented Oct 29, 2024

pull-cloud-provider-aws-e2e tests are failing due to breaching a limit:

2024-10-29T00:09:21.633296227Z stderr F W1029 00:09:21.633191       1 aws.go:2522] Error opening ingress rules for the load balancer to the instances: "error authorizing security group ingress: \"RulesPerSecurityGroupLimitExceeded: The maximum number of rules per security group has been reached.\\n\\tstatus code: 400, request id: c4f650b1-bc77-40e3-b9a5-6f6efcf3ea01\""

We're seeing this in all of the tests, but the pull-cloud-provider-aws-e2e tests are the only ones explicitly failing. Someone with access to the account needs to do the following:

  1. Go to AWS Console
  2. Navigate to "Service Quotas" in the us-west-2 region
  3. Select Amazon Virtual Private Cloud (Amazon VPC) as the service
  4. Request an increase for Inbound or outbound rules per security group
@mmerkes mmerkes added the sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. label Oct 29, 2024
@dims
Copy link
Member

dims commented Oct 29, 2024

current setting:

image

@dims
Copy link
Member

dims commented Oct 29, 2024

Here's the bump requested:

image

@dims
Copy link
Member

dims commented Oct 29, 2024

@mmerkes almost there!

I’m happy to inform you that we have approved and processed your VPC limit increase request for Rules per VPC Security Group in the US West (Oregon) region, and your new limit is 200 while the Security groups per interface limit is still 5.

Please keep in mind that it can sometimes take up to 30 minutes for the new limit to take effect and become available for use.

@mmerkes
Copy link
Author

mmerkes commented Oct 29, 2024

Sweet! Tx @dims. I'll stop trying by restarting tests then and demonstrate some patience!

@mmerkes
Copy link
Author

mmerkes commented Oct 29, 2024

Still seeing the issue @dims

Error authorizing security group ingress "RulesPerSecurityGroupLimitExceeded: The maximum number of rules per security group has been reached.

Did you apply to account 209411653980?

@dims
Copy link
Member

dims commented Oct 29, 2024

image

@dims
Copy link
Member

dims commented Oct 29, 2024

@mmerkes see screen shot above. yep i see the new service quota changes in there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
None yet
Development

No branches or pull requests

2 participants