Can I create extra private subnets without tagging them?

[Israphel]

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

• Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

We use EKS, and there's a feature to use a secondary CIDR block only for the pods. In order to do that, you create a secondary CIDR block and extra private subnets associated to that. All of that is supported by this module.
However, for EKS users it's typical to have private subnet tags related to AWS load balancer and/or Karpenter. But, the subnets which are specific for the pods can't be tagged with those values, or they will be autodiscovered and used for something they shouldn't.

Describe the solution you'd like.

Someway to create "extra" private subnets but without being affected by the private subnet tags.

Describe alternatives you've considered.

I made a small module that creates subnets and route table associations, so I'm managing my vpc with this module plus that one.

Additional context

[jpulgar4]

We're having the same exact issue, a separate solution might be to allow to tag a subgroup of subnets instead perhaps?

[jlewis-spotnana]

We have a similar issue, where we want to tag some (but not all) of our public and private subnets for Kubernetes. I'll put a PR together later this week if time allows.

UPDATE 1:
Hmm... There is a PR on this already, but it was closed due to inactivity. #1139 Can someone reopen this PR?

UPDATE 2:
@antonbabenko ☝

[github-actions]

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days