Jaeger operator pod restarting in RHOCP 4

Solution Verified - Updated -

Issue

  • The jaeger operator pod is restarting with OOMKilled:

    $ oc get pods  -n openshift-distributed-tracing -l name=jaeger-operator -o yaml 
NAME                               READY   STATUS    RESTARTS   AGE
jaeger-operator-5bfdc966bf-28kt4   2/2     Running   161        25h

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • Red Hat OpenShift Distributed Tracing Platform (RHOSDT)
    • 2.8

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