Bug 1888118

Summary: Memory requests not specified for image registry operator
Product: OpenShift Container Platform Reporter: Ricardo Maraschini <rmarasch>
Component: Image RegistryAssignee: Oleg Bulatov <obulatov>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.6CC: aos-bugs
Target Milestone: ---   
Target Release: 4.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: the operator pod does not have memory requests Consequence: in case of memory pressure on the node, the operator might be OOM-killed before other BestEffort containers Fix: add memory request Result: the operator won't be killed if there are other BestEffort containers on the node
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-24 15:25:41 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:
Embargoed:

Description Ricardo Maraschini 2020-10-14 06:30:48 UTC
Description of problem:

By default openshift does not specify memory requests and limits for the image registry operator.


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

4.6

How reproducible:

Always


Steps to Reproduce:
1. oc get -o json pod operator-pod |jq ".spec.containers[].resources"

Actual results:

{
  "requests": {
    "cpu": "10m"
  }
}

Expected results:

{
  "requests": {
    "cpu": "10m"
    "memory": "<some value>"
  },
  "limits": {
    "cpu": "10m"
    "memory": "<some value>"
  }
}

Comment 1 Oleg Bulatov 2020-10-14 14:38:54 UTC
The operator doesn't need limits. So expected results:

{
  "requests": {
    "cpu": "10m"
    "memory": "<some value>"
  }
}

Comment 3 Wenjing Zheng 2020-10-26 07:44:45 UTC
$ oc get -o json pod cluster-image-registry-operator-5b6f5ff8b-rwwgp |jq ".spec.containers[].resources"
{
  "requests": {
    "cpu": "10m",
    "memory": "50Mi"
  }
}
Verified on 4.7.0-0.nightly-2020-10-24-155529.

Comment 6 errata-xmlrpc 2021-02-24 15:25:41 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.7.0 security, bug fix, and enhancement 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-2020:5633