Bug 1822351

Summary:	fix hybrid proxier to not force constant resyncing
Product:	OpenShift Container Platform	Reporter:	Dan Winship <danw>
Component:	Networking	Assignee:	Dan Winship <danw>
Networking sub component:	openshift-sdn	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	huirwang
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:26:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dan Winship 2020-04-08 19:22:21 UTC

We did a bunch of patches upstream to make kube-proxy not do constant unnecessary iptables resyncs but then didn't notice that our hybrid proxier code was forcing unnecessary resyncs anyway.

Acceptance criteria:
- Cluster still works
- Services still work, still reflect new/changed/deleted endpoints promptly
- Service idling/unidling still works, still changes state promptly
- Monitoring the kubeproxy_sync_proxy_rules_last_timestamp_seconds metric on the sdn pod shows that it only changes when there are actual changes to services/endpoints, rather than automatically being updated every 30 seconds.

Comment 4 errata-xmlrpc 2020-07-13 17:26:34 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409