Amazon VPC CNI now supports automatic subnet discovery

You can now leverage tag-based subnet discovery capability of [Amazon VPC CNI](https://github.com/aws/amazon-vpc-cni-k8s) to scale Amazon Elastic Kubernetes Service (EKS) clusters in IPv4 address space without adding operational complexity. In this new default mode, Kubernetes Pod IP addresses are allocated from all tagged and available subnets in your Amazon Virtual Private Cloud(VPC). Modernizing your applications using Amazon EKS, you are likely looking for ways to optimize IPv4 address space consumption and maximize usage of your VPC CIDRs as well as subnets provisioned for the EKS Pods. Now, Amazon VPC CNI based automatic subnet discovery for Pod IP assignment helps you streamline your network configuration by dynamically allocating IP addresses within defined subnets. You can tag subnets and integrate them seamlessly into an existing EKS cluster networking configuration. Once tagged, Amazon VPC CNI will automatically discover the new VPC subnets with available IP address space and use them to allocate IP addresses for Kubernetes Pods in an EKS cluster. Starting with Amazon VPC CNI version 1.18.0, support for enhanced subnet discovery is available in all regions where Amazon EKS operates. To learn more, check out the [launch blog](https://aws.amazon.com/blogs/containers/amazon-vpc-cni-introduces-enhanced-subnet-discovery/) and to get started, visit the Amazon EKS [documentation](https://docs.aws.amazon.com/eks/latest/userguide/managing-vpc-cni.html).