KubeScheduler not scheduling pods in RHOCP 4

Solution Verified - Updated -

Issue

  • Pods remain in Pending state and not getting scheduled to any nodes:

    NAME                       READY   STATUS    RESTARTS   AGE     IP       NODE     NOMINATED NODE   READINESS GATES
    controller-manager-gzbf4   0/1     Pending   0          130m    <none>   <none>   <none>           <none>
    controller-manager-lz5tr   0/1     Pending   0          3h45m   <none>   <none>   <none>           <none>
    controller-manager-rt4kf   0/1     Pending   0          3h45m   <none>   <none>   <none>           <none>
    
  • Logs like the following ones are shown in the kube-scheduler pods:

    k8s.io/kubernetes/cmd/kube-scheduler/app/server.go:246: Failed to list *v1.Pod: Unauthorized
    
    vendor/k8s.io/client-go/informers/factory.go:134: Failed to watch *v1.Pod: failed to list *v1.Pod: Unauthorized
    
  • Certificate errors are shown in the kube-apiserver logs:

    Unable to authenticate the request
    
    x509: certificate signed by unknown authority, verifying certificate
    

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