-
Notifications
You must be signed in to change notification settings - Fork 208
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
connectivity: add egress-gateway-with-l7-policy test #2578
connectivity: add egress-gateway-with-l7-policy test #2578
Conversation
8bda315
to
1e249fd
Compare
All tests have passed with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct me if I'm wrong: it seems the PR is doing two different things, 1) test egress-gw with L7 policy; 2) add testcase to assert egress-gw's SNAT for pod-to-external-service traffic. I would suggest splitting into two commits if that's the case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good for my CODEOWNERS
This test case checks if the traffic selected by an egress gateway policy is masqueraded with an Egress IP when the clients send a request using DNS. The case is mainly to check the compatibility of Egress Gateway and L7 policy. Signed-off-by: Yusuke Suzuki <[email protected]>
egress-gateway-with-l7-policy checks if traffic from Pods that are selected by both Egress Gateway Policy and L7 Network Policy is properly SNATed with an Egress IP. Signed-off-by: Yusuke Suzuki <[email protected]>
1e249fd
to
a89f5af
Compare
Looks like multicluster is flaky |
egress-gateway-with-l7-policy checks if traffic from Pods that are selected by both Egress Gateway Policy and L7 Network Policy is properly SNATed with an Egress IP.
cilium/cilium#32828