We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is your idea request related to a problem that you've solved? Please describe.
The networking section discusses the InsufficientIPAddress problem, but doesn't include this newer option announced in April '24.
InsufficientIPAddress
Amazon VPC CNI version 1.18.0 supports Enhanced Subnet Discovery. It is less configuration overhead than custom networking.
https://aws.amazon.com/blogs/containers/amazon-vpc-cni-introduces-enhanced-subnet-discovery/
Describe the best practice
See the blog post for specifics on usage + implementation.
Describe alternatives you've considered
See the blog post for alternatives - custom networking is still a better solution for specific use cases.
The text was updated successfully, but these errors were encountered:
Tim-AWS
No branches or pull requests
Is your idea request related to a problem that you've solved? Please describe.
The networking section discusses the
InsufficientIPAddress
problem, but doesn't include this newer option announced in April '24.Amazon VPC CNI version 1.18.0 supports Enhanced Subnet Discovery. It is less configuration overhead than custom networking.
https://aws.amazon.com/blogs/containers/amazon-vpc-cni-introduces-enhanced-subnet-discovery/
Describe the best practice
See the blog post for specifics on usage + implementation.
Describe alternatives you've considered
See the blog post for alternatives - custom networking is still a better solution for specific use cases.
The text was updated successfully, but these errors were encountered: