kubernetes_cluster_events_parte02

gistfile1.txt

# kubectl get events --all-namespaces --sort-by=.metadata.creationTimestamp
NAMESPACE     LAST SEEN   TYPE      REASON           OBJECT                                           MESSAGE
default       59m         Normal    Pulling          pod/busybox                                      Pulling image "busybox"
default       59m         Normal    Created          pod/busybox                                      Created container busy
default       59m         Normal    Started          pod/busybox                                      Started container busy
default       59m         Normal    Pulled           pod/busybox                                      Successfully pulled image "busybox" in 1.606189033s
kube-system   4m55s       Warning   Unhealthy        pod/kube-apiserver-kubernetes-cluster            Liveness probe failed: HTTP probe failed with statuscode: 500
kube-system   62s         Warning   Unhealthy        pod/kube-apiserver-kubernetes-cluster            Readiness probe failed: HTTP probe failed with statuscode: 500
kube-system   5m32s       Warning   Unhealthy        pod/etcd-kubernetes-cluster                      Liveness probe failed: Get "http://127.0.0.1:2381/health": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
kube-system   5m31s       Warning   Unhealthy        pod/kube-controller-manager-kubernetes-cluster   Liveness probe failed: HTTP probe failed with statuscode: 500
kube-system   112s        Normal    Pulled           pod/kube-scheduler-kubernetes-cluster            Container image "k8s.gcr.io/kube-scheduler:v1.24.1" already present on machine
kube-system   112s        Normal    Pulled           pod/kube-controller-manager-kubernetes-cluster   Container image "k8s.gcr.io/kube-controller-manager:v1.24.1" already present on machine
kube-system   48s         Warning   Unhealthy        pod/kube-controller-manager-kubernetes-cluster   Liveness probe failed: Get "https://127.0.0.1:10257/healthz": dial tcp 127.0.0.1:10257: connect: connection refused
kube-system   48s         Warning   Unhealthy        pod/kube-scheduler-kubernetes-cluster            Liveness probe failed: Get "https://127.0.0.1:10259/healthz": dial tcp 127.0.0.1:10259: connect: connection refused
kube-system   91s         Normal    Started          pod/kube-scheduler-kubernetes-cluster            Started container kube-scheduler
kube-system   94s         Normal    Created          pod/kube-scheduler-kubernetes-cluster            Created container kube-scheduler
kube-system   86s         Normal    Started          pod/kube-controller-manager-kubernetes-cluster   Started container kube-controller-manager
kube-system   90s         Normal    Created          pod/kube-controller-manager-kubernetes-cluster   Created container kube-controller-manager
kube-system   4m32s       Warning   Unhealthy        pod/kube-controller-manager-kubernetes-cluster   Startup probe failed: Get "https://127.0.0.1:10257/healthz": dial tcp 127.0.0.1:10257: connect: connection refused
kube-system   45s         Warning   Unhealthy        pod/etcd-kubernetes-cluster                      Liveness probe failed: HTTP probe failed with statuscode: 503
kube-system   4m40s       Warning   Unhealthy        pod/kube-scheduler-kubernetes-cluster            Startup probe failed: Get "https://127.0.0.1:10259/healthz": net/http: TLS handshake timeout
kube-system   4m11s       Normal    LeaderElection   lease/kube-scheduler                             kubernetes-cluster_89f79cdd-6fef-4c26-9b3f-25104760b864 became leader
kube-system   4m2s        Normal    LeaderElection   lease/kube-controller-manager                    kubernetes-cluster_78910679-f769-4513-866d-73edb955d46a became leader
kube-system   18s         Warning   BackOff          pod/kube-controller-manager-kubernetes-cluster   Back-off restarting failed container
kube-system   9s          Warning   BackOff          pod/kube-scheduler-kubernetes-cluster            Back-off restarting failed container
kube-system   2m40s       Normal    LeaderElection   lease/kube-controller-manager                    kubernetes-cluster_3aa07ccf-b135-4e93-a581-efefead6fb74 became leader
kube-system   2m36s       Normal    LeaderElection   lease/kube-scheduler                             kubernetes-cluster_5d07ab64-c129-4107-9b6e-395804ec5506 became leader
kube-system   59s         Normal    LeaderElection   lease/kube-controller-manager                    kubernetes-cluster_c72a8440-1e61-4fdf-92e8-9d05ea345fa6 became leader
kube-system   59s         Normal    LeaderElection   lease/kube-scheduler                             kubernetes-cluster_8159a672-c6ef-473c-947b-eba63d6b2fd9 became leader