Skip to content

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

Closed as not planned
@Constantin07

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions