compliance-operator v0.1.57 is failing with OOMKilled and CrashLoopBackOff

Solution Verified - Updated -

Issue

  • compliance-operator v0.1.57 with default memory limits is being OOMKilled and is stuck in a CrashLoopBackOff.
  • compliance-operator v0.1.57 pod is OOMKilled shortly after startup
  • compliance-operator v0.1.57 pod is OOMKilled after running for a few hours
  • In clusters with a large number of namespaces the compliance-operator v0.1.57 pod is OOMKilled very quickly

Environment

  • Red Hat OpenShift Container Platform 4
  • Red Hat OpenShift Compliance Operator v0.1.57

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