Currently we have cpu/memory limits set on config-reloader but we shouldn't: $ kubectl -n openshift-monitoring get sts alertmanager-main -o yaml | grep -A4 config-reloader name: config-reloader resources: limits: cpu: 100m memory: 25Mi We should also most likely have an e2e test asserting that no limits are being set.
These are the default settings from Prometheus operator. I'm thinking we should fix this upstream and default to no limits instead of the current values. The same limit is also present for Prometheus instances.
Tested with 4.5.0-0.nightly-2020-03-16-004817, there is not cpu/memory limits set on config-reloader # kubectl -n openshift-monitoring get sts alertmanager-main -o yaml | grep -A4 config-reloader name: config-reloader resources: {} terminationMessagePath: /dev/termination-log terminationMessagePolicy: FallbackToLogsOnError volumeMounts:
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-2020:2409