Description of problem: operator registry appears to be growing in memory size. This ticket has an attached PR to cleanup row closes. https://github.com/operator-framework/operator-registry/pull/570 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
verify: zhaoxia@wangshanshandeMacBook-Pro community-operators % oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-02-26-221801 True False 74m Cluster version is 4.8.0-0.nightly-2021-02-26-221801 zhaoxia@wangshanshandeMacBook-Pro community-operators % monitor memory usage. https://user-images.githubusercontent.com/77608951/109466365-8fc1cc80-7aa4-11eb-8d6d-9b89567641bc.png https://user-images.githubusercontent.com/77608951/109466707-1b3b5d80-7aa5-11eb-8276-2d5d38a2ec15.png https://user-images.githubusercontent.com/77608951/109468375-70786e80-7aa7-11eb-8c71-c28be4f5100f.png verified.
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.8.2 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-2021:2438