fix: ipv6 egress route for single nat #1227
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
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 ?