Details
-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.11.z
-
None
-
Important
-
No
-
Rejected
-
False
-
Description
Description of problem:
The static pod of kube-apiserver-guard keeps a not ready status which needs SRE to restart the master to fix the problem
Version-Release number of selected component (if applicable):
4.11.34
How reproducible:
Steps to Reproduce:
oc get co NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE kube-apiserver 4.11.34 True True True 257d MissingStaticPodControllerDegraded: static pod lifecycle failure - static pod: "kube-apiserver" in namespace: "openshift-kube-apiserver" for revision: 87 on node: "ip-10-110-136-109.ap-southeast-2.compute.internal" didn't show up, waited: 5m44s oc get pods -n openshift-kube-apiserver NAME READY STATUS RESTARTS AGE installer-84-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 13d installer-84-ip-10-110-137-90.ap-southeast-2.compute.internal 0/1 Completed 0 13d installer-84-ip-10-110-138-43.ap-southeast-2.compute.internal 0/1 Completed 0 13d installer-85-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 5d12h installer-87-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 14h kube-apiserver-guard-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Running 0 14d kube-apiserver-guard-ip-10-110-137-90.ap-southeast-2.compute.internal 1/1 Running 0 14d kube-apiserver-guard-ip-10-110-138-43.ap-southeast-2.compute.internal 1/1 Running 0 14d kube-apiserver-ip-10-110-136-109.ap-southeast-2.compute.internal 5/5 Running 0 13d kube-apiserver-ip-10-110-137-90.ap-southeast-2.compute.internal 5/5 Running 0 13d kube-apiserver-ip-10-110-138-43.ap-southeast-2.compute.internal 5/5 Running 0 13d revision-pruner-83-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 14d revision-pruner-83-ip-10-110-137-90.ap-southeast-2.compute.internal 0/1 Completed 0 14d revision-pruner-83-ip-10-110-138-43.ap-southeast-2.compute.internal 0/1 Completed 0 14d revision-pruner-84-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 13d revision-pruner-84-ip-10-110-137-90.ap-southeast-2.compute.internal 0/1 Completed 0 13d revision-pruner-84-ip-10-110-138-43.ap-southeast-2.compute.internal 0/1 Completed 0 13d revision-pruner-85-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 5d12h revision-pruner-85-ip-10-110-137-90.ap-southeast-2.compute.internal 0/1 Completed 0 5d12h revision-pruner-85-ip-10-110-138-43.ap-southeast-2.compute.internal 0/1 Completed 0 5d12h revision-pruner-86-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 14h revision-pruner-86-ip-10-110-137-90.ap-southeast-2.compute.internal 0/1 Completed 0 14h revision-pruner-86-ip-10-110-138-43.ap-southeast-2.compute.internal 0/1 Completed 0 14h revision-pruner-87-ip-10-110-136-109.ap-southeast-2.compute.internal 0/1 Completed 0 14h revision-pruner-87-ip-10-110-137-90.ap-southeast-2.compute.internal 0/1 Completed 0 14h revision-pruner-87-ip-10-110-138-43.ap-southeast-2.compute.internal 0/1 Completed 0 14h