-
Notifications
You must be signed in to change notification settings - Fork 3.4k
cilium-cli: extend no-interrupted-connections to test Egress Gateway #38193
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
Conversation
83134b8
to
905ea00
Compare
/test |
905ea00
to
ae37941
Compare
/test |
ae37941
to
92d57b7
Compare
/test |
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.
Thanks! A couple of minor comments inline.
The new test is being skipped in CI. I would prefer to see a run where it passes before approving. https://github.com/cilium/cilium/actions/runs/13890711080/job/38862132656#step:27:258 |
3f81844
to
8c89991
Compare
/test |
This commit extends the conn-disrupt-test to ensure that connections through a Egress Gateway are not disrupted. The test deploys a conn-disrupt-test server with a single replica on an external node, a client on a gateway node and another client on a non gateway node. Clients establish long-lived TCP connections with the server through the gateway node. After upgrade, the test checks the restart counters, and compares them with the counters stored before the upgrade. A mismatch indicates that a connection was interrupted. Example output from `kubectl -n cilium-test-1 get po -o wide`: ``` NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES test-conn-disrupt-client-egw-gw-node-859d6b6875-vkvh2 1/1 Running 0 15s 10.244.3.206 kind-worker <none> <none> test-conn-disrupt-client-egw-non-gw-node-6c69d885df-7z6c5 1/1 Running 0 15s 10.244.1.14 kind-worker2 <none> <none> test-conn-disrupt-server-egw-644f65cb-vz8v7 1/1 Running 0 17s 172.18.0.4 kind-worker3 <none> <none> ``` Signed-off-by: Yusuke Suzuki <yusuke.suzuki@isovalent.com>
This commit enables conn-disrupt-test for Egress Gateway. Signed-off-by: Yusuke Suzuki <yusuke.suzuki@isovalent.com>
Restarting the agent disrupts the connection through the EGW when lb-acceleration is enabled due to #37431 Let's skip it for now Signed-off-by: Yusuke Suzuki <yusuke.suzuki@isovalent.com>
Currently, the cross-cluster EGW policies are not supported. Let's skip it for now. Signed-off-by: Yusuke Suzuki <yusuke.suzuki@isovalent.com>
8c89991
to
656594e
Compare
/test |
@pippolo84 Gentle ping for review🙏 |
Sorry for the delay, I'm gonna review this tomorrow 👍 |
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.
Nice! 🚀
This PR extends the conn-disrupt-test to ensure that connections through a Egress Gateway are not disrupted.
The test deploys a conn-disrupt-test server with a single replica on an external node, a client on a gateway node and another client on a non gateway node. Clients establish long-lived TCP connections with the server through the gateway node.
After upgrade, the test checks the restart counters, and compares them with the counters stored before the upgrade. A mismatch indicates that a connection was interrupted.
Example output from
kubectl -n cilium-test-1 get po -o wide
:Fixes: #37092