Warning message

A translation for your language preference does not exist.

kube-scheduler not scheduling pods due to client certificate not renewed automatically in OpenShift 4

Solution Vérifié - Mis à jour -

Question

  • How to renew the kube-scheduler client certificate if it is not automatically rotated?

  • What to do when pods remain in Pending status and kube-scheduler log shows errors like:

    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

Environnement

  • 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