Skip to content

fix: ipv6 egress route for single nat #1227

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jbatmalle
Copy link

@jbatmalle jbatmalle commented Jul 23, 2025

Description

After merged PR #1059, in the case of a single NAT with multiple private networks, only the route for the first network is retained; the others are removed. This behavior has changed.

Exemple

private_subnets = [
   "10.0.0.0/24", "10.0.1.0/24", "10.0.2.0/24",
   "10.0.3.0/24", "10.0.4.0/24", "10.0.5.0/24",
]
 
private_subnet_ipv6_prefixes = [
   1, 2, 3,
   4, 5, 6
]
enable_nat_gateway     = true
single_nat_gateway     = true
one_nat_gateway_per_az = false
create_egress_only_igw = true

Motivation and Context

I'm upgrading from v2.78 to v5.21. The issue was introduced in v5.7.1.

Why is this change required? What problem does it solve?

Otherwise, the first private route resource is retained (NAT gateway count equals 1), while the subsequent private routes are removed.

Breaking Changes

no

How Has This Been Tested?

I have tested on my code

Other thing

Could you create a new v5 version ?

@jbatmalle jbatmalle changed the title fix ipv6 egress route for single nat fix: ipv6 egress route for single nat Jul 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant