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

Allow using IPs from assigned prefix to ENI in case of security groups usage #3013

Open
aenshin-pp opened this issue Aug 22, 2024 · 5 comments

Comments

@aenshin-pp
Copy link

What would you like to be added:
I'd like to have ability to use more IPs, therefore run more Pods with security groups on a node.

Why is this needed:
To make security/network management easier and reduce cost by utilizing nodes.

@orsenthil
Copy link
Member

Allow using IPs from assigned prefix to ENI in case of security groups usage

Hi @aenshin-pp , could you explain this a bit more. How are you are currently using in your setup and what kind of enhancement would you desire?

@aenshin-pp
Copy link
Author

aenshin-pp commented Aug 26, 2024

@orsenthil

The following article mentions our issue at "Comparison to security groups for pods":
https://aws.amazon.com/blogs/containers/amazon-vpc-cni-increases-pods-per-node-limits/

We have vanilla EKS with VPC CNI and use security groups. No big modifications.
It might limit us with IP number as mentioned in article or below issues:

aws/containers-roadmap#1153
aws/containers-roadmap#1342

All dated 2020-2021, few years old.

I wonder if there is a solution to use security groups in EKS and also be able to use more IPs than branch ENIs available for particular instance type (e.g. use prefixes)?

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days

@github-actions github-actions bot added the stale Issue or PR is stale label Oct 26, 2024
Copy link

github-actions bot commented Nov 9, 2024

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 9, 2024
@aenshin-pp
Copy link
Author

@catlike hi from kube con :)

@orsenthil orsenthil reopened this Nov 29, 2024
@github-actions github-actions bot removed the stale Issue or PR is stale label Nov 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants