kube-scheduler pod revision roll-out stuck on OpenShift Container Platform 4

Solution Verified - Updated -

Issue

  • kube-scheduler Cluster Operartor (CO) is in degraded state in OCP cluster and one of the kube-scheduler pods is in CrashLoopBackOff state with the following error:

    2021-02-09T16:11:04.817431552Z couldn't get policy config map openshift-kube-scheduler/policy-configmap: Get https://localhost:6443/api/v1/namespaces/openshift-kube-scheduler/configmaps/policy-configmap: x509: certificate signed by unknown authority

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