Add CNI Autodiscovery Tags to Subnets Generated from Secondary CIDR Blocks #1251
Description
Describe the solution you'd like.
According to the documentation on enhanced subnet discovery in VPC CNI (assuming I'm reading it correctly; https://aws.amazon.com/blogs/containers/amazon-vpc-cni-introduces-enhanced-subnet-discovery/), subnets generated from secondary CIDR blocks need to be tagged with "Key=kubernetes.io/role/cni, Value=1" to be auto-discovered. This is simple enough to do from the CLI, but I don't see a way to do it in the module when setting secondary_cidr_block.
Is there a way to tag subnets created from secondary CIDR blocks (via the module) of if not, could this be added? I see there are similar requests about tagging subnets, but nothing this specific.
Describe alternatives you've considered.
Might also be able to do this manually by creating and assigning subnets using TF resources, but the VPC module would be easier/cleaner.