Re-deploying named certificates with new CA causes nodes to go into NotReady state in OpenShift Container Platform 3.11

Solution Verified - Updated -


Red Hat OpenShift Container Platform nodes remain in status `NotReady`after running [Redeploying Master Certificates](
The service `atomic-openshift-node` start reporting an error loading the `/etc/origin/node/client-ca.crt` and `oc` commands gives error `Unable to connect to the server: x509: certificate signed by unknown authority`


  • Red Hat OpenShift Container Platform (RHOCP)
    • 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