The kube-apiserver CO goes in degraded state in RHOCP 4

Solution Verified - Updated -

Issue

  • The kube-apiserver ClusterOperator is degraded:
$ oc get co kube-apiserver
kube-apiserver                             4.12.39  True        True          True       528d    StaticPodsDegraded: pod/kube-apiserver-master1.lab.example.com container "kube-apiserver" is waiting: CrashLoopBackOff: back-off 5m0s restarting failed container=kube-apiserver pod=kube-apiserver-master1.lab.example.com_openshift-kube-apiserver(54b6574996eadd96975b71f4a1d2aab0)...
  • The kube-apiserver pod is in CrashLoopBackOff state:
$ oc get po -n openshift-kube-apiserver
kube-apiserver-master1.lab.example.com         3/5     CrashLoopBackOff   839 (61s ago)   6h48m
  • The kube-apiserver pod reporting the below error:
 $ oc -n openshift-kube-apiserver logs -c kube-apiserver kube-apiserver-master1.lab.example.com  
E1117 15:52:07.330326      17 run.go:74] "command failed" err="tls: private key does not match public key"

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