test:
openshift-tests.[sig-api-machinery][Feature:APIServer][Late] kube-apiserver terminates within graceful termination period   [1] 

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?search=%5C%5Bsig-api-machinery%5C%5D%5C%5BFeature%3AAPIServer%5C%5D%5C%5BLate%5C%5D+kube-apiserver+terminates+within+graceful+termination+period&maxAge=168h&context=1&type=bug%2Bjunit&name=4.7&maxMatches=5&maxBytes=20971520&groupBy=job


https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/promote-release-openshift-okd-machine-os-content-e2e-aws-4.7/1352233058454999040

fail [github.com/onsi/ginkgo.0-origin.1+incompatible/internal/leafnodes/runner.go:64]: kube-apiserver didn't terminate by itself during the graceful termination period: v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"kube-apiserver-ip-10-0-134-168.us-west-2.compute.internal.165c418d0b87848c", GenerateName:"", Namespace:"openshift-kube-apiserver", SelfLink:"/api/v1/namespaces/openshift-kube-apiserver/events/kube-apiserver-ip-10-0-134-168.us-west-2.compute.internal.165c418d0b87848c", UID:"2ef54c62-8637-45f9-b74a-f0d776c447de", ResourceVersion:"21464", Generation:0, CreationTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63746831640, loc:(*time.Location)(0x94f5720)}}, DeletionTimestamp:(*v1.Time)(nil), DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ClusterName:"", ManagedFields:[]v1.ManagedFieldsEntry{v1.ManagedFieldsEntry{Manager:"watch-termination", Operation:"Update", APIVersion:"v1", Time:(*v1.Time)(0xc0034a0a40), FieldsType:"FieldsV1", FieldsV1:(*v1.FieldsV1)(0xc0034a0a60)}}}, InvolvedObject:v1.ObjectReference{Kind:"Pod", Namespace:"openshift-kube-apiserver", Name:"kube-apiserver-ip-10-0-134-168.us-west-2.compute.internal", UID:"", APIVersion:"v1", ResourceVersion:"", FieldPath:""}, Reason:"GracefulTerminationTimeout", Message:"kube-apiserver did not terminate within 2m15s", Source:v1.EventSource{Component:"apiserver", Host:"ip-10-0-134-168"}, FirstTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63746831640, loc:(*time.Location)(0x94f5720)}}, LastTimestamp:v1.Time{Time:time.Time{wall:0x0, ext:63746831640, loc:(*time.Location)(0x94f5720)}}, Count:1, Type:"Warning", EventTime:v1.MicroTime{Time:time.Time{wall:0x0, ext:0, loc:(*time.Location)(nil)}}, Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}. This is a bug in kube-apiserver. It probably means that network connections are not closed cleanly, and this leads to network I/O timeout errors in other components.