OpenShift Compliance Operator ocp4-cis pods in a NotReady or CrashLoopBackoff state

Solution Verified - Updated -

Issue

  • Some Compliance Operator pods are stuck in a CrashLoopBackoff while some run without issue
  • The ocp4-cis pods are in a NotReady 1/2 state moving through a CrashLoopBackoff

Environment

  • Red Hat OpenShift Container Platform (OCP) 4.5+

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