-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Update instance type networking limits #1153
Conversation
@@ -209,7 +218,7 @@ g5.12xlarge 737 | |||
g5.16xlarge 234 | |||
g5.24xlarge 737 | |||
g5.2xlarge 58 | |||
g5.48xlarge 737 | |||
g5.48xlarge 345 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea, I just ran the VPC CNI script: https://github.com/aws/amazon-vpc-cni-k8s/blob/master/scripts/gen_vpc_ip_limits.go and saw that it pulled a new limit here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
based on the change in pkg/awsutils/vpc_ip_resource_limit.go in this PR, the ENILimit for g5.48xlarge changed from 15 to 7, double confirmed by checking DescribeInstanceTypes
API, see the response of NetworkInfo for g5.48xlarge below
"NetworkInfo": {
"NetworkPerformance": "100 Gigabit",
"MaximumNetworkInterfaces": 7,
"MaximumNetworkCards": 1,
"DefaultNetworkCardIndex": 0,
"NetworkCards": [
{
"NetworkCardIndex": 0,
"NetworkPerformance": "100 Gigabit",
"MaximumNetworkInterfaces": 7
}
],
"Ipv4AddressesPerInterface": 50,
"Ipv6AddressesPerInterface": 50,
"Ipv6Supported": true,
"EnaSupport": "required",
"EfaSupported": true,
"EfaInfo": {
"MaximumEfaInterfaces": 1
},
"EncryptionInTransitSupported": true,
"EnaSrdSupported": false
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah nice, thank you for checking!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty odd that this changed, but the API doesn't lie. 👍
Issue #, if available:
N/A
Description of changes:
Updates instance networking limits in
eni-max-pods.txt
. Mirrors aws/amazon-vpc-cni-k8s#2235By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Testing Done
N/A