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
delete stale UDP conntrack entries for loadbalancer IPs #104009
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @thockin @danwinship |
/sig network |
sort.Strings(expectedCommands) | ||
sort.Strings(actualCommands) | ||
|
||
if !reflect.DeepEqual(expectedCommands, actualCommands) { |
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.
this is flake free
$ go test -timeout 100s -run ^TestProxierDeleteNodePortStaleUDP$ k8s.io/kubernetes/pkg/proxy/iptables -c
$ stress ./iptables.test
105 runs so far, 0 failures
@aojea thank for the fix! 😄 Do you think this is important enough to get ported into v1.20 🙏🏼 |
yeah, I think it qualifies |
/sig network |
/lgtm |
/sig network |
/ok-to-test |
/retest |
/test pull-kubernetes-integration |
@aojea happy to see this passing and getting merged! I see two cherry picks linked here for 1.22 and 1.21, is there any chance to see a 1.20 cherry pick as well? |
is not your fault, I had to cherry pick it from a cherry pick, that is why it didn't show up here, |
/triage accepted |
…9-upstream-release-1.22 Automated cherry pick of #104009: delete stale UDP conntrack entries for loadbalancer IPs
…9-upstream-release-1.21 Automated cherry pick of #104009: delete stale UDP conntrack entries for loadbalancer IPs
/kind bug
What this PR does / why we need it:
From the long saga of UDP conntrack stale entries breaking services, we have a new chapter because I forget to consider the lb ingress IPs
Fixes: #103857