subnet: fix nat outgoing policy rule #3003
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zhangzujian
force-pushed
the
fix-nat
branch
2 times, most recently
from
a7ce751
to
9a2ffe4
Compare
changluyi
approved these changes
Jul 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of this PR
Which issue(s) this PR fixes:
Fixes #(issue-number)
WHAT
🤖 Generated by Copilot at a36e85c
This pull request enhances the NAT outgoing policy feature for subnets in kube-ovn. It improves the subnet controller logic, the gateway daemon implementation, and the e2e test case for the feature. It also refactors some code and fixes some bugs related to the feature.
🤖 Generated by Copilot at a36e85c
HOW
🤖 Generated by Copilot at a36e85c
Sha256ByteToStringfunction toSha256Hashinpkg/util/strings.go(link)test/e2e/kube-ovn/subnet/subnet.go(link, link, link, link, link, link, link, link, link)