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
k8sT/Egress: fixes #17581
k8sT/Egress: fixes #17581
Conversation
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.
Changes from original PR look good to me. The error you had previously looked unrelated to that particular test so probably an issue in your local setup. 🤞 it'll pass on the first try after the rebase.
/test |
4756405
to
6101c8a
Compare
/test |
/test-gke edit: GKE was failing with, which should be fixed.
|
/test-1.21-4.9 edit: after investigation, failure (was on policies) seemed unrelated, so redoing test. |
1433181 introduced a change in GenerateNamespaceForTest which is not needed. This patch reverts it. Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
6101c8a
to
665a9d9
Compare
/test |
Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
665a9d9
to
29d3737
Compare
/test-only --focus="K8sEgress" |
/test-only --focus="K8sEgress.*" |
/test |
/test-only --focus=".K8sEgressGateway." |
I think our script for |
The |
Ah, right. That's because you need to pass the appropriate |
29d3737
to
2388d4e
Compare
/test |
Signed-off-by: Kornilios Kourtis <kornilios@isovalent.com>
Tests are green. Will open for reviews, and will try to reproduce #17604 using a focus test. |
/test-only --focus=".K8sEgressGateway." --kernel-version="net-next" |
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.
LGTM! One nit below but not worth addressing IMO unless there are other comments.
/test-only --focus=".K8sEgressGateway." --kernel_version="net-next" It's |
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.
👍🏻
|
The last attempt to run the focus test, also does not seem to work: https://jenkins.cilium.io/job/Cilium-PR-Tests-Kernel-Focus/321/console:
In any case, I'll mark this as |
Weirdly enough, that build was trigered by @nbusseneau's comment 🤔 (CTRL+F for @kkourt Your build is at https://jenkins.cilium.io/job/Cilium-PR-Tests-Kernel-Focus/320/console and failed because of the |
That one should work: |
This PR includes fixes for the k8sT/egress test. It is a followup PR for #17517 (review).
Updates:
@pchaigno noticed that the context helper was wrong, which lead to some kubectl commands being called with an empty namespace. In addition to that, I've added another commit to print the egress and nat tables in case of a failure. This is meant to help identify potential issues as reported in CI: v1.10: K8sEgressGatewayTest tunnel disabled with endpoint routes enabled Checks egress policy and basic connectivity both work: curl failed to connect with exit code 28 #17604.
turns out that starting cilium at the begging was actually needed. fix the patch to just add a comment.
removed
=
from tests names, to avoid:agent bailed out with:
adjusted configuration accordingly