Bug 2086143 - CNO uses too much memory
Summary: CNO uses too much memory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Ben Bennett
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-14 06:13 UTC by Casey Callendrello
Modified: 2022-08-10 11:12 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:12:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 1431 0 None Merged Bug 2086143: Status controller: use a label, rather than watching all objects 2022-07-15 20:12:56 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:12:11 UTC

Description Casey Callendrello 2022-05-14 06:13:48 UTC 
On large clusters, CNO uses gigabytes of memory. This is absurd.

One of the problems is that it watches all daemonsets, deployments, and stateful sets. There are probably some other bad watches in there too.
Comment 4 zhaozhanqi 2022-05-24 02:07:21 UTC 
verified this bug.
Comment 7 errata-xmlrpc 2022-08-10 11:12:00 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 (Important: OpenShift Container Platform 4.11.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.

https://access.redhat.com/errata/RHSA-2022:5069
Note You need to log in before you can comment on or make changes to this bug.