Bug 1769807

Summary: Use protobuf in SDN clients to reduce CPU usage
Product: OpenShift Container Platform Reporter: Dan Winship <danw>
Component: NetworkingAssignee: Clayton Coleman <ccoleman>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified    
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1769808 (view as bug list) Environment:
Last Closed: 2020-01-23 11:11:43 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:
Bug Depends On:    
Bug Blocks: 1769808    

Description Dan Winship 2019-11-07 14:34:23 UTC
openshift-sdn was using JSON-only k8s clients because earlier releases did not support using protobuf clients to work with CRD types. This is apparently fixed in k8s 1.16.

I don't know if it's worth bothering testing the fix beyond "things still work" but if so, Clayton can fill in the expected difference in metrics output.

Comment 1 Clayton Coleman 2019-11-07 14:44:04 UTC
We were running during an e2e test about ~1.4-1.8 cores for all SDN containers across all 6 nodes. We are now running about 1.1 to 1.4 cores.  In heavily used clusters this will be more impactful.

Comment 2 Clayton Coleman 2019-11-07 14:44:13 UTC
We were running during an e2e test about ~1.4-1.8 cores for all SDN containers across all 6 nodes. We are now running about 1.1 to 1.4 cores.  In heavily used clusters this will be more impactful.

Comment 4 errata-xmlrpc 2020-01-23 11:11:43 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:0062