Apr 09 13:17:46.730 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.apps.openshift.io: not available: failing or missing response from https://10.128.0.73:8443/apis/apps.openshift.io/v1: Get "https://10.128.0.73:8443/apis/apps.openshift.io/v1": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    Apr 09 13:18:01.727 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.build.openshift.io: not available: failing or missing response from https://10.128.0.73:8443/apis/build.openshift.io/v1: Get "https://10.128.0.73:8443/apis/build.openshift.io/v1": context deadline exceeded
    Apr 09 13:18:16.874 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.apps.openshift.io: not available: failing or missing response from https://10.129.0.50:8443/apis/apps.openshift.io/v1: Get "https://10.129.0.50:8443/apis/apps.openshift.io/v1": context deadline exceeded\nAPIServicesAvailable: apiservices.apiregistration.k8s.io/v1.project.openshift.io: not available: failing or missing response from https://10.128.0.73:8443/apis/project.openshift.io/v1: Get "https://10.128.0.73:8443/apis/project.openshift.io/v1": dial tcp 10.128.0.73:8443: i/o timeout
    Apr 09 13:25:10.247 - 25s   E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "apps.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "authorization.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "build.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "image.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "project.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "quota.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "route.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "security.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "template.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)
    Apr 09 13:31:25.504 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.apps.openshift.io: not available: failing or missing response from https://10.128.0.10:8443/apis/apps.openshift.io/v1: Get "https://10.128.0.10:8443/apis/apps.openshift.io/v1": context deadline exceeded
    Apr 09 13:31:45.328 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.build.openshift.io: not available: failing or missing response from https://10.130.0.14:8443/apis/build.openshift.io/v1: Get "https://10.130.0.14:8443/apis/build.openshift.io/v1": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Mar 23 00:06:22.588 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: "security.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 23 00:06:22.588 - 101ms E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "security.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 23 00:08:05.974 E ns/openshift-kube-controller-manager pod/installer-7-ip-10-0-152-28.us-east-2.compute.internal node/ip-10-0-152-28.us-east-2.compute.internal uid/4d94aaa0-c495-4bf5-9b31-3744e8aeb84b container/installer reason/ContainerExit code/1 cause/Error ng) (len=8 cap=8) {\n  (string) (len=27) "kube-controller-manager-pod",\n  (string) (len=6) "config",\n  (string) (len=32) "cluster-policy-controller-config",\n  (string) (len=29) "controller-manager-kubeconfig",\n  (string) (len=38) "kube-controller-cert-syncer-kubeconfig",\n  (string) (len=17) "serviceaccount-ca",\n  (string) (len=10) "service-ca",\n  (string) (len=15) "recycler-config"\n },\n OptionalConfigMapNamePrefixes: ([]string) (len=1 cap=1) {\n  (string) (len=12) "cloud-config"\n },\n CertSecretNames: ([]string) (len=2 cap=2) {\n  (string) (len=39) "kube-controller-manager-client-cert-key",\n  (string) (len=10) "csr-signer"\n },\n OptionalCertSecretNamePrefixes: ([]string) <nil>,\n CertConfigMapNamePrefixes: ([]string) (len=2 cap=2) {\n  (string) (len=20) "aggregator-client-ca",\n  (string) (len=9) "client-ca"\n },\n OptionalCertConfigMapNamePrefixes: ([]string) (len=1 cap=1) {\n  (string) (len=17) "trusted-ca-bundle"\n },\n CertDir: (string) (len=66) "/etc/kubernetes/static-pod-resources/kube-controller-manager-certs",\n ResourceDir: (string) (len=36) "/etc/kubernetes/static-pod-resources",\n PodManifestDir: (string) (len=25) "/etc/kubernetes/manifests",\n Timeout: (time.Duration) 2m0s,\n StaticPodManifestsLockFile: (string) "",\n PodMutationFns: ([]installerpod.PodMutationFunc) <nil>,\n KubeletVersion: (string) ""\n})\nI0323 00:07:34.676459       1 cmd.go:410] Getting controller reference for node ip-10-0-152-28.us-east-2.compute.internal\nI0323 00:07:34.775026       1 cmd.go:423] Waiting for installer revisions to settle for node ip-10-0-152-28.us-east-2.compute.internal\nI0323 00:07:34.779081       1 cmd.go:515] Waiting additional period after revisions have settled for node ip-10-0-152-28.us-east-2.compute.internal\nI0323 00:07:36.856737       1 cmd.go:124] Received SIGTERM or SIGINT signal, shutting down the process.\nI0323 00:08:04.779158       1 cmd.go:521] Getting installer pods for node ip-10-0-152-28.us-east-2.compute.internal\nF0323 00:08:04.779270       1 cmd.go:106] client rate limiter Wait returned an error: context canceled\n

Mar 23 00:06:22.588 - 101ms E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "security.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request