Bug 2117569

Summary: kube-controller-manager needs to stop watching all events
Product: OpenShift Container Platform Reporter: Michal Fojtik <mfojtik>
Component: kube-controller-managerAssignee: Ben Luddy <bluddy>
Status: CLOSED ERRATA QA Contact: zhou ying <yinzhou>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.12CC: mfojtik
Target Milestone: ---Keywords: FastFix
Target Release: 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Event objects in the events.k8s.io/v1 group were unnecessarily being watched by the garbage collection controller. In a case of unbound Event creation (e.g. due to a runaway controller), this could result in degraded performance. The garbage collection controller now ignores Events.
Story Points: ---
Clone Of:
: 2118318 (view as bug list) Environment:
Last Closed: 2023-01-17 19:54:46 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:
Bug Depends On:    
Bug Blocks: 2117679, 2118318    

Description Michal Fojtik 2022-08-11 10:42:49 UTC
Description of problem:

The garbage collector must ignore ALL events; otherwise, if a rouge controller or a workload causes unbound event creation, GC performance will degrade as it has to process the events.

Fix: https://github.com/openshift/kubernetes/pull/1338

This bug is to track fix in master (4.12) and also allow to backport to 4.11.1

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 6 errata-xmlrpc 2023-01-17 19:54:46 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 (Moderate: OpenShift Container Platform 4.12.0 bug fix and security update), and where to find the updated
files, follow the link below.

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