When deploying a new Red Hat 3scale APIcast self-managed instance on OpenShift Container Platform (OCP), the pod fails with "CrashLoopBackOff" and no errors on the logs

Solution Verified - Updated -


We are deploying APIcast self-managed to connect to a Red Hat 3scale 2.X On-premises instance. We created the Access Token and tested connectivity between the APIcast and the 3scale Backend. We set the Environment Variable APICAST_LOG_LEVEL=debug, but this doesn't show what is going on. The pod is being killed with the status CrashLoopBackOff.


  • Red Hat 3scale API Management
    • 2.X On-premises

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