-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Create pod on a node with no more IP #5317
Comments
@DanielCastronovo you should be using Prefix Delegation which will expand the number of IPs available on a node by quite a lot |
Potentially related #5234 |
@njtran i don't think it is related to subnets, but to ec2 ENI capacity. |
Agreed, was pointing to your comment about running out of IPs in the subnets. |
I was just trying to provide extra general guidance |
Fine, thanks for your help :) |
Description
Observed Behavior:
When a pod is created, they are an issue because the instance size has no more IP. Like M instance size (8 IP address limits)
Expected Behavior:
Assign a node type related to the limits on nodes IP address.
Reproduction Steps (Please include YAML):
Versions:
kubectl version
): 1.27The text was updated successfully, but these errors were encountered: