Bug 1762301 - [3.11] backport kube-proxy fix for spurious connection resets
Summary: [3.11] backport kube-proxy fix for spurious connection resets
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.z
Assignee: Dan Winship
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On: 1762298
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-16 13:07 UTC by Dan Winship
Modified: 2020-01-21 08:08 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1762298
Environment:
Last Closed: 2020-01-21 08:08:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan Winship 2019-10-16 13:07:38 UTC
+++ This bug was initially created as a clone of Bug #1762298 +++

https://github.com/kubernetes/kubernetes/pull/74840 fixed a problem in kube-proxy where if certain TCP ACKs got lost (eg because there's a lot of traffic and so some packets are getting dropped) then the connection might be spuriously closed when kube-proxy received an unexpected retransmit.

There's not an easy way to test this but it's a simple patch, and it appears to have fixed the problem for the original filers, and the fix went into kube 1.15 and hasn't caused problems for anyone else, and now we have a customer who would like it backported.

Comment 1 Dan Winship 2020-01-21 08:08:04 UTC
closing because the corresponding 4.1 bug (bug 1762300) was closed... if we decide to backport this we can reopen both


Note You need to log in before you can comment on or make changes to this bug.