🥳 aws-vpc-cni v1.18.0 Automated Release! 🥑 #1083
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
aws-vpc-cni v1.18.0 Automated Chart Sync! 🤖🤖
Release Notes 📝:
v1.18.0
Release Notes
VPC-CNI now supports enhanced subnet discovery - A default mode in which pod IP addresses are allocated from all tagged and available subnets. This is aimed at helping increase the number of available IPv4 addresses and scale your workloads in IP constrained environments.
Changes since v1.17.1
To manually apply this release:
Note that the following regions use different manifests:
us-gov-east-1:
us-gov-west-1:
cn:
To apply this release using helm:
Follow the installation instructions in https://github.com/aws/amazon-vpc-cni-k8s/blob/v1.18.0/charts/aws-vpc-cni/README.md#installing-the-chart
Verify the update: