apiserver pod from kube-service-catalog project in crashloopbackoff state
Issue
apiserver
pod is crashing on one master while it is running fine on other 2 master nodes
[root@host ~]# oc get pods -n kube-service-catalog
NAME READY STATUS RESTARTS AGE
apiserver-5bx5x 1/1 Running 1 65d
apiserver-9t9v4 1/1 Running 1 65d
apiserver-skxgr 0/1 CrashLoopBackOff 4153 65d
controller-manager-5h4tp 1/1 Running 1 65d
controller-manager-jsfnm 1/1 Running 1 65d
controller-manager-qdss5 1/1 Running 4 65d
- Pod logs shows:
[root@host ~]# oc logs pod/apiserver-skxgr -n kube-service-catalog
I0808 12:50:31.146375 1 feature_gate.go:194] feature gates: map[OriginatingIdentity:true]
I0808 12:50:31.146591 1 feature_gate.go:194] feature gates: map[NamespacedServiceBroker:true OriginatingIdentity:true]
I0808 12:50:31.146617 1 hyperkube.go:192] Service Catalog version v3.11.98;Upstream:v0.1.35 (built 2019-03-19T16:37:37Z)
W0808 12:50:31.878101 1 authentication.go:245] Unable to get configmap/extension-apiserver-authentication in kube-system. Usually fixed by 'kubectl create rolebinding -n kube-system ROLE_NAME --role=extension-apiserver-authentication-reader --serviceaccount=YOUR_NS:YOUR_SA'
Error: Get https://192.168.0.1:443/api/v1/namespaces/kube-system/configmaps/extension-apiserver-authentication: dial tcp 192.168.0.1:443: connect: network is unreachable
Environment
- OpenShift Container Platform 3.11
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.