Bug 1641815

Summary:	service-serving-cert-signer is making high amounts of requests
Product:	OpenShift Container Platform	Reporter:	Juan Vallejo <jvallejo>
Component:	apiserver-auth	Assignee:	Matt Rogers <mrogers>
Status:	CLOSED ERRATA	QA Contact:	scheng
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, evb, jokerman, mkhan, mmccomas, mrogers, nagrawal, wsun
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:40:48 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:

Description Juan Vallejo 2018-10-22 20:48:45 UTC

Description of problem:

The service-serving-cert-signer is making over 30,000 requests within the span of 2 hours (since bringing up a cluster using the installer).

For comparison, the apiserver performs 24,000 requests within the same time period.

Comment 1 Matt Rogers 2018-10-30 01:31:28 UTC

Hi Juan, try running your metrics with docker.io/mrogers950/origin-service-serving-cert-signer:limittest ? This is an image built with https://github.com/openshift/service-serving-cert-signer/pull/37. We should see a reduction in the amount of API requests over time.

Comment 2 Neelesh Agrawal 2019-01-25 21:19:42 UTC

I think we had couple of rounds of reduction on request-load. Is this still an active issue? Can this be closed now?

Comment 3 Matt Rogers 2019-01-25 21:34:33 UTC

Yes, the operator no longer continually sync loops, which was the root cause of our constant API hammering.

Comment 8 errata-xmlrpc 2019-06-04 10:40:48 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:0758