Support for new AWS VPC CNI custom subnets used by EKS Pods from secondary CIDR range

[Constantin07]

Is your request related to a problem? Please describe.

This is feature request for adding a new type of subnets in VPC - specifically the one used EKS pods (VPC CNI Custom networking) from VPC secondary CIDR range.

Why?

I want to have a distinct subnets for EKS Pods from CG-NAT space, i.e. 100.64.0.0/10.
They should be routable via NAT Gateway, etc. as Pods need access to internet (similar to elasticache).

Describe the solution you'd like.

Being able to define in vpc module something like:

module "vpc" {
...
    # VPC CNI custom subnets for EKS pods
    customcni_subnets            = ...
    customcni_subnet_names = ...

Describe alternatives you've considered.

At the moment I'm using elasticsearch subnets but this is a bit misleading in name.

module "vpc" {
...
    # Using elasticsearch subnets for EKS pods network as intra ones have no outbound access via NAT Gateway
    elasticache_subnets            = ...
    elasticache_subnet_names = ...

Additional context

EKS Custom Networking
AWS CNI Custom networking

[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

[Constantin07]

/remove stale

[ForbiddenEra]

See my comment in #918 as well but I think #892 should be considered as a potential way forward for handling subnets; if not exactly how suggested there, at least improving the flexibility should be considered, it seems like a few users are wanting more flexibility with subnet groups/their naming/etc.

[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

[Constantin07]

/remove stale

[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

[Constantin07]

/remove stale

[ForbiddenEra]

/preemptive remove stale ;)

[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

[github-actions]

This issue was automatically closed because of stale in 10 days

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.