Router pods going into CrashLoopBackOff state and restarting frequently after replacing the default ingress certificate in RHOCP 4

Solution Verified - Updated -

Issue

  • After replacing the default ingress certificate, the router pods are not coming up healthy:
$ oc get pods -n openshift-ingress
NAME                             READY  STATUS   RESTARTS  AGE
router-default-7bcb8c489b-94vjf  0/1    Running  221       19h
router-default-7bcb8c489b-kvl72  0/1    Running  205       17h

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4

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