-
Notifications
You must be signed in to change notification settings - Fork 193
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
workflows: add test exceptions to EKS tunnel workflow #450
Conversation
4b863d4
to
9f0671c
Compare
3bb05c0
to
f62974c
Compare
f62974c
to
763c6e8
Compare
315bde2
to
a8a38aa
Compare
a8a38aa
to
923ee17
Compare
Following merge of #251, testing on EKS in tunnel mode is now reliably broken due to an issue in upstream: cilium/cilium#16975 This type of failure was already happening before #251, but the PR made it very evident as before we were only running checks from a few random pods (which would sometimes work) and are now running checks from all pods, drastically increasing the chance of hitting at least one failure. Since the test setup is not to blame and this is an actual issue with Cilium in tunnel momde, we disable the failing tests until upstream issue is fixed. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
923ee17
to
7b4af33
Compare
Link to working test run of the changes in the EKS tunnel workflow: https://github.com/cilium/cilium-cli/actions/runs/1056560809 |
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, should provide some breathing room in the mean time. 👍
ok let's ship it |
It seems this is just happening because of leftover iptables rules from aws-node. I confirmed the full connectivity tests pass locally on EKS+overlay once the rules are removed. See cilium/cilium#26897 (comment) for details. We can probably revert this and should even support removal of those rules in the CLI IMO. |
Following merge of #251, testing on EKS in tunnel mode is now reliably broken due to an issue in upstream: cilium/cilium#16975
This type of failure was already happening before #251, but the PR made it very evident as before we were only running checks from a few random pods (which would sometimes work) and are now running checks from all pods, drastically increasing the chance of hitting at least one failure.
Since the test setup is not to blame and this is an actual issue with Cilium in tunnel mode, we disable the failing tests until upstream issue is fixed.