Logging-Kibana Pod Runs Out Of Memory

Solution Verified - Updated -


  • Noticed that the kibana container, within the logging-kibana pod keeps going OOM, and restarting every 1.5-2 hours.
  • It looks like a new environment variable KIBANA_MEMORY_LIMIT was added to the dc/logging-kibana deployment configuration. It appears to be setting the memory to 736 MB.
  • Kibana pod is terminating with exit code 137 (OOMKilled)


  • RedHat OpenShift Container Platform
    • 3.5
    • 3.11

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