Observability Operator pod is failing in RHOCP 4

Solution Verified - Updated -

Issue

  • Observability operator pod is failing continuously.

  • Pod is in CrashLoopBackOff with OOMKilled:

    $ oc get pods -n openshift-cluster-observability-operator | grep -v "Running"
observability-operator-xxxx                      0/1     CrashLoopBackOff

    $ oc get pod <observability-operator-pod-name> -o json -n openshift-cluster-observability-operator | jq .status
----- Output Omitted -----
       exitCode: 137     
       reason: OOMKilled

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Cluster Observability Operator (COO)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content