Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1769808

Summary:	[4.2] Use protobuf in SDN clients to reduce CPU usage
Product:	OpenShift Container Platform	Reporter:	Dan Winship <danw>
Component:	Networking	Assignee:	Clayton Coleman <ccoleman>
Networking sub component:	openshift-sdn	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	cdc
Version:	4.3.0
Target Milestone:	---
Target Release:	4.2.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1769807	Environment:
Last Closed:	2019-12-03 22:43:15 UTC	Type:	---
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:	1769807
Bug Blocks:

Description Dan Winship 2019-11-07 14:35:43 UTC

+++ This bug was initially created as a clone of Bug #1769807 +++

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 Casey Callendrello 2019-11-15 16:36:46 UTC

We just use separate configs for network vs. core types, so we can safely switch one of them to protobuf.

Comment 3 zhaozhanqi 2019-11-22 07:06:38 UTC

From the e2e testing in 4.2 nightly 4.2.0-0.nightly-2019-11-22-005934
this bug can be verified.

Comment 5 errata-xmlrpc 2019-12-03 22:43:15 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-2019:3953