Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-8715

Implement resource.requests in operator pod spec

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • Log Collection
    • None
    • Future Sustainability
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • NEW
    • NEW
    • If Release Note Needed, Set a Value

      Best Practices 2 of 2 remaining items

      New test results run on 4.20-rose:  
      https://cert-track-results-cert-tracker--runtime-int.apps.gpc.ocp-hub.prod.psi.redhat.com/releases/4/operators/4?sort=type&order=asc

      Failed message
      "container: cluster-logging-operator pod: cluster-logging-operator-b5bd486b-plnh6 ns: openshift-logging" is missing resource requests

       

      • The CPU request typically defines a weighting. If several different containers (cgroups) want to run on a contended system, workloads with larger CPU requests are allocated more CPU time than workloads with small requests.
      • The memory request is mainly used during (Kubernetes) Pod scheduling. On a node that uses cgroups v2, the container runtime might use the memory request as a hint to set memory.min and memory.low.

              Unassigned Unassigned
              cahartma@redhat.com Casey Hartman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: