Bug 1721685

Summary: node-ca pod is missing resource requests
Product: OpenShift Container Platform Reporter: Derek Carr <decarr>
Component: Image RegistryAssignee: Oleg Bulatov <obulatov>
Status: CLOSED ERRATA QA Contact: Wenjing Zheng <wzheng>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, wewang
Target Milestone: ---   
Target Release: 4.1.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: add resources request to node-ca pod Reason: the pod needs minimal guarantees about the amount of CPU and memory it will get Result: node-ca pod has resources request
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-31 02:44:55 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:

Description Derek Carr 2019-06-18 21:28:06 UTC
Description of problem:
the image registry operator that deploys the node ca pod is not including resource requests.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 wewang 2019-07-25 07:53:47 UTC
verified in 4.2.0-0.nightly-2019-07-23-002801

$ oc describe pod node-ca-48srg  -n openshift-image-registry

    Restart Count:  1
    Requests:
      cpu:        10m
      memory:     10Mi
    Environment:  <none>
    Mounts:

Comment 5 wewang 2019-07-25 07:54:51 UTC
and will check it in 4.1.x

Comment 6 wewang 2019-07-25 07:58:16 UTC
Verified in 
4.1.0-0.nightly-2019-07-24-213555

$oc describe pod node-ca-57z9f -n openshift-image-registry
    Requests:
      cpu:        10m
      memory:     10Mi
    Environment:  <none>
    Mounts:

Comment 8 errata-xmlrpc 2019-07-31 02:44:55 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, 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-2019:1866