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

Support multiple subnets in custom networking mode #3008

Closed
adammw opened this issue Aug 7, 2024 · 2 comments
Closed

Support multiple subnets in custom networking mode #3008

adammw opened this issue Aug 7, 2024 · 2 comments
Labels

Comments

@adammw
Copy link
Contributor

adammw commented Aug 7, 2024

What would you like to be added:
Change the schema of Custom Networking mode configuration CRDs (ENIConfig) to support specifying multiple subnets. At runtime, use the same logic as Custom Networking to have each interface attachment pick the subnet with the most number of free IPs.

Why is this needed:
Subnet discovery is incompatible with Custom Networking mode - for full control over which pods on which nodes get attached to which subnets, Custom Networking mode is the only way. However this means we cannot specify multiple subnets and get the CNI plugin to pick the subnet with the most number of free IPs. Adding multiple subnets to the CRD would allow the CNI to choose from a specific list of subnets rather than need to discover the subnets using tags.

Copy link

github-actions bot commented Oct 6, 2024

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 6, 2024
Copy link

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant