Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[migrated] secondary CIDR blocks #633

Open
geoffcline opened this issue Jan 14, 2025 · 0 comments
Open

[migrated] secondary CIDR blocks #633

geoffcline opened this issue Jan 14, 2025 · 0 comments
Labels
correction Data is inaccurate help wanted Extra attention is needed

Comments

@geoffcline
Copy link
Collaborator

Migrated from internal customer ticket

The notion that custom networking in EKS by adding secondary CIDR blocks to a VPC from the 198.19.0.0/16 ranges, in conjunction with the CNI Custom Networking feature is not the present case. According to VPC documentation, you cannot associate 198.19.0.0/16 range as secondary CIDR to any existing VPC CIDR range including CIDR from RFC 1918 range, CIDR from CG NAT or Publicly routable CIDR block (non-RFC 1918). See https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html I also validated this to be true.

page: https://docs.aws.amazon.com/en_us/eks/latest/best-practices/custom-networking.html

@geoffcline geoffcline added correction Data is inaccurate help wanted Extra attention is needed labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correction Data is inaccurate help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant