Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1957291

Summary: Performance addon operator pod should have CPU and memory requests set but not limits
Product: OpenShift Container Platform Reporter: Tinashe Chipomho <tchipomh>
Component: Performance Addon OperatorAssignee: Martin Sivák <msivak>
Status: CLOSED CURRENTRELEASE QA Contact: Gowrishankar Rajaiyan <grajaiya>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.7CC: aos-bugs, dgonyier, fromani, keyoung, mniranja, shajmakh, vlaad
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2019924 (view as bug list) Environment:
Last Closed: 2022-08-26 14:14:42 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:
Bug Depends On:    
Bug Blocks: 1945258, 2019924    

Comment 2 Martin Sivák 2021-06-10 10:28:45 UTC
*** Bug 1945258 has been marked as a duplicate of this bug. ***

Comment 3 Niranjan Mallapadi Raghavender 2021-07-06 02:48:58 UTC
[root@bkr-hv03 ~]# oc version
Client Version: 4.8.0-rc.2
Server Version: 4.8.0-rc.2
Kubernetes Version: v1.21.0-rc.0+1622f87

PAO Version:
++ skopeo inspect docker://registry-proxy.engineering.redhat.com/rh-osbs/openshift4-performance-addon-rhel8-operator@sha256:b514fe2ce4fde4d2ca393eb3fef83849154d75d60788d7ee5d02b1bc9e0a863f
+ LABELS='{
  "architecture": "x86_64",
  "build-date": "2021-06-30T07:04:04.978914",
  "com.redhat.build-host": "cpt-1007.osbs.prod.upshift.rdu2.redhat.com",
  "com.redhat.component": "performance-addon-operator-container",
  "com.redhat.license_terms": "https://www.redhat.com/agreements",
  "description": "performance-addon-operator",
  "distribution-scope": "public",
  "io.k8s.description": "performance-addon-operator",
  "io.k8s.display-name": "performance-addon-operator",
  "io.openshift.expose-services": "",
  "io.openshift.maintainer.component": "Performance Addon Operator",
  "io.openshift.maintainer.product": "OpenShift Container Platform",
  "io.openshift.tags": "operator",
  "maintainer": "openshift-operators",
  "name": "openshift4/performance-addon-rhel8-operator",
  "release": "45",
  "summary": "performance-addon-operator",
  "upstream-vcs-ref": "cbdb661ab1fac2cd74e7df9155a70ba4ebeddba1",
  "upstream-vcs-type": "git",
  "upstream-version": "4.5.0-0.beta.0-745-gcbdb661",
  "url": "https://access.redhat.com/containers/#/registry.access.redhat.com/openshift4/performance-addon-rhel8-operator/images/v4.8.0-45",
  "vcs-ref": "39ca315b6c41ca107fa3e864e8f226e62b547796",
  "vcs-type": "git",
  "vendor": "Red Hat, Inc.",
  "version": "v4.8.0"
}'

Check the PAO Pod:

[root@bkr-hv03 ~]# oc get pods
NAME                                    READY   STATUS    RESTARTS   AGE
performance-operator-5c9cd7896d-zd7s2   1/1     Running   0          6m8s

Get the pod spec:

spec:
  affinity:
    nodeAffinity:  
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: node-role.kubernetes.io/master
            operator: Exists
  containers:
  - command:
    - performance-operator
    env:
    - name: WATCH_NAMESPACE
      valueFrom:   
        fieldRef:  
          apiVersion: v1
          fieldPath: metadata.annotations['olm.targetNamespaces']
    - name: POD_NAME
      valueFrom:   
        fieldRef:  
          apiVersion: v1
          fieldPath: metadata.name
    - name: OPERATOR_NAME
      value: performance-operator
    - name: OPERATOR_CONDITION_NAME
      value: performance-addon-operator.v4.8.0
    image: registry.redhat.io/openshift4/performance-addon-rhel8-operator@sha256:b514fe2ce4fde4d2ca393eb3fef83849154d75d60788d7ee5d02b1bc9e0a863f
    imagePullPolicy: Always
    name: performance-operator
    resources:
      requests:
        cpu: 10m   
        memory: 25Mi
    securityContext:
      capabilities:
        drop:
        - KILL
        - MKNOD
        - SETGID   
        - SETUID   
      runAsUser: 1000630000

As seen in the above output, PAO pod now contains cpu and memory requests and no limits set.