Time Namespace Component Host RelatedObject Reason Message
default my-nginx-646554d7fd-5llxc Scheduled Successfully assigned default/my-nginx-646554d7fd-5llxc to ip-172-31-0-147.ec2.internal
kube-system coredns-6fccb86bcb-5n4bj Scheduled Successfully assigned kube-system/coredns-6fccb86bcb-5n4bj to ip-172-31-15-25.ec2.internal
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal Starting Starting kubelet.
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeAllocatableEnforced Updated Node Allocatable limit across pods
(x7) default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasSufficientPID Node ip-172-31-15-25.ec2.internal status is now: NodeHasSufficientPID
(x7) default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasNoDiskPressure Node ip-172-31-15-25.ec2.internal status is now: NodeHasNoDiskPressure
(x8) default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasSufficientMemory Node ip-172-31-15-25.ec2.internal status is now: NodeHasSufficientMemory
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal InvalidDiskCapacity invalid capacity 0 on image filesystem
kube-system kubelet ip-172-31-15-25.ec2.internal etcd-ip-172-31-15-25.ec2.internal Created Created container etcd
kube-system kubelet ip-172-31-15-25.ec2.internal kube-controller-manager-ip-172-31-15-25.ec2.internal Created Created container kube-controller-manager
kube-system kubelet ip-172-31-15-25.ec2.internal etcd-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal kube-controller-manager-ip-172-31-15-25.ec2.internal Started Started container kube-controller-manager
kube-system kubelet ip-172-31-15-25.ec2.internal kube-scheduler-ip-172-31-15-25.ec2.internal Created Created container kube-scheduler
kube-system kubelet ip-172-31-15-25.ec2.internal kube-scheduler-ip-172-31-15-25.ec2.internal Started Started container kube-scheduler
kube-system kubelet ip-172-31-15-25.ec2.internal etcd-ip-172-31-15-25.ec2.internal Started Started container etcd
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/kube-apiserver:v1.27.3" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal Created Created container kube-apiserver
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal Started Started container kube-apiserver
kube-system kubelet ip-172-31-15-25.ec2.internal kube-controller-manager-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/kube-controller-manager:v1.27.3" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal kube-scheduler-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/kube-scheduler:v1.27.3" already present on machine
kube-system kube-controller-manager kube-controller-manager LeaderElection ip-172-31-15-25.ec2.internal_7931953c-6447-43bd-bb41-898c8c942568 became leader
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal InvalidDiskCapacity invalid capacity 0 on image filesystem
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasSufficientMemory Node ip-172-31-15-25.ec2.internal status is now: NodeHasSufficientMemory
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasSufficientPID Node ip-172-31-15-25.ec2.internal status is now: NodeHasSufficientPID
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeAllocatableEnforced Updated Node Allocatable limit across pods
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasNoDiskPressure Node ip-172-31-15-25.ec2.internal status is now: NodeHasNoDiskPressure
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal Starting Starting kubelet.
kube-system default-scheduler kube-scheduler LeaderElection ip-172-31-15-25.ec2.internal_d893f416-2658-42ec-8f19-986e08464854 became leader
kube-system node-controller kube-scheduler-ip-172-31-15-25.ec2.internal NodeNotReady Node is not ready
kube-system node-controller kube-apiserver-ip-172-31-15-25.ec2.internal NodeNotReady Node is not ready
default node-controller ip-172-31-15-25.ec2.internal RegisteredNode Node ip-172-31-15-25.ec2.internal event: Registered Node ip-172-31-15-25.ec2.internal in Controller
kube-system node-controller etcd-ip-172-31-15-25.ec2.internal NodeNotReady Node is not ready
kube-system node-controller kube-controller-manager-ip-172-31-15-25.ec2.internal NodeNotReady Node is not ready
kube-system replicaset-controller coredns-5d78c9869d SuccessfulCreate Created pod: coredns-5d78c9869d-74hvm
kube-system replicaset-controller coredns-5d78c9869d SuccessfulCreate Created pod: coredns-5d78c9869d-wxj65
kube-system deployment-controller coredns ScalingReplicaSet Scaled up replica set coredns-5d78c9869d to 2
(x6) kube-system default-scheduler coredns-5d78c9869d-74hvm FailedScheduling 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
(x6) kube-system default-scheduler coredns-5d78c9869d-wxj65 FailedScheduling 0/1 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/not-ready: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling..
kube-system replicaset-controller cilium-operator-84985fb6b9 SuccessfulCreate Created pod: cilium-operator-84985fb6b9-26kqh
kube-system default-scheduler cilium-operator-84985fb6b9-mwd4n FailedScheduling 0/1 nodes are available: 1 node(s) didn't match pod anti-affinity rules. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod..
kube-system default-scheduler cilium-n9qs5 Scheduled Successfully assigned kube-system/cilium-n9qs5 to ip-172-31-15-25.ec2.internal
kube-system default-scheduler cilium-operator-84985fb6b9-26kqh Scheduled Successfully assigned kube-system/cilium-operator-84985fb6b9-26kqh to ip-172-31-15-25.ec2.internal
kube-system replicaset-controller cilium-operator-84985fb6b9 SuccessfulCreate Created pod: cilium-operator-84985fb6b9-mwd4n
kube-system deployment-controller cilium-operator ScalingReplicaSet Scaled up replica set cilium-operator-84985fb6b9 to 2
kube-system daemonset-controller cilium SuccessfulCreate Created pod: cilium-n9qs5
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-operator-84985fb6b9-26kqh Unhealthy Readiness probe failed: Get "http://127.0.0.1:9234/healthz": dial tcp 127.0.0.1:9234: connect: connection refused
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-operator-84985fb6b9-26kqh Pulled Container image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container config
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container config
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-operator-84985fb6b9-26kqh Created Created container cilium-operator
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-operator-84985fb6b9-26kqh Started Started container cilium-operator
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container mount-cgroup
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container mount-cgroup
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container apply-sysctl-overwrites
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container apply-sysctl-overwrites
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container mount-bpf-fs
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container mount-bpf-fs
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container clean-cilium-state
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container clean-cilium-state
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container install-cni-binaries
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container install-cni-binaries
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container cilium-agent
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container cilium-agent
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container cilium-monitor
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container cilium-monitor
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Unhealthy Startup probe failed: Get "http://127.0.0.1:9879/healthz": dial tcp 127.0.0.1:9879: connect: connection refused
kube-system default-scheduler coredns-5d78c9869d-74hvm Scheduled Successfully assigned kube-system/coredns-5d78c9869d-74hvm to ip-172-31-15-25.ec2.internal
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeReady Node ip-172-31-15-25.ec2.internal status is now: NodeReady
kube-system default-scheduler coredns-5d78c9869d-wxj65 Scheduled Successfully assigned kube-system/coredns-5d78c9869d-wxj65 to ip-172-31-15-25.ec2.internal
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-wxj65 Pulled Container image "registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-74hvm Created Created container coredns
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-74hvm Pulled Container image "registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-wxj65 Started Started container coredns
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-wxj65 Created Created container coredns
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-74hvm Started Started container coredns
kube-system daemonset-controller cilium SuccessfulCreate Created pod: cilium-5qxnr
(x5) default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeHasNoDiskPressure Node ip-172-31-0-147.ec2.internal status is now: NodeHasNoDiskPressure
(x5) default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeHasSufficientPID Node ip-172-31-0-147.ec2.internal status is now: NodeHasSufficientPID
(x5) default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeHasSufficientMemory Node ip-172-31-0-147.ec2.internal status is now: NodeHasSufficientMemory
kube-system default-scheduler cilium-operator-84985fb6b9-mwd4n Scheduled Successfully assigned kube-system/cilium-operator-84985fb6b9-mwd4n to ip-172-31-0-147.ec2.internal
kube-system default-scheduler cilium-5qxnr Scheduled Successfully assigned kube-system/cilium-5qxnr to ip-172-31-0-147.ec2.internal
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container config
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-84985fb6b9-mwd4n Started Started container cilium-operator
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-84985fb6b9-mwd4n Created Created container cilium-operator
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-84985fb6b9-mwd4n Pulled Container image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container config
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
default node-controller ip-172-31-0-147.ec2.internal RegisteredNode Node ip-172-31-0-147.ec2.internal event: Registered Node ip-172-31-0-147.ec2.internal in Controller
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container mount-cgroup
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container mount-cgroup
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container apply-sysctl-overwrites
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container apply-sysctl-overwrites
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container mount-bpf-fs
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container mount-bpf-fs
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container clean-cilium-state
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container clean-cilium-state
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container install-cni-binaries
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container install-cni-binaries
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container cilium-agent
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container cilium-agent
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container cilium-monitor
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container cilium-monitor
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Unhealthy Startup probe failed: Get "http://127.0.0.1:9879/healthz": dial tcp 127.0.0.1:9879: connect: connection refused
default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeReady Node ip-172-31-0-147.ec2.internal status is now: NodeReady
(x5) default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasSufficientPID Node ip-172-31-8-188.ec2.internal status is now: NodeHasSufficientPID
(x5) default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasNoDiskPressure Node ip-172-31-8-188.ec2.internal status is now: NodeHasNoDiskPressure
(x5) default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasSufficientMemory Node ip-172-31-8-188.ec2.internal status is now: NodeHasSufficientMemory
kube-system default-scheduler cilium-htj82 Scheduled Successfully assigned kube-system/cilium-htj82 to ip-172-31-8-188.ec2.internal
kube-system daemonset-controller cilium SuccessfulCreate Created pod: cilium-htj82
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container config
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container config
default node-controller ip-172-31-8-188.ec2.internal RegisteredNode Node ip-172-31-8-188.ec2.internal event: Registered Node ip-172-31-8-188.ec2.internal in Controller
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container mount-cgroup
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container mount-cgroup
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container apply-sysctl-overwrites
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container apply-sysctl-overwrites
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container mount-bpf-fs
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container mount-bpf-fs
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container clean-cilium-state
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container clean-cilium-state
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container install-cni-binaries
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container install-cni-binaries
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container cilium-agent
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container cilium-agent
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container cilium-monitor
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container cilium-monitor
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Unhealthy Startup probe failed: Get "http://127.0.0.1:9879/healthz": dial tcp 127.0.0.1:9879: connect: connection refused
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeReady Node ip-172-31-8-188.ec2.internal status is now: NodeReady
kube-system deployment-controller cilium-operator ScalingReplicaSet Scaled up replica set cilium-operator-5d6bff587 to 2 from 1
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-84985fb6b9-mwd4n Unhealthy Readiness probe failed: Get "http://127.0.0.1:9234/healthz": dial tcp 127.0.0.1:9234: connect: connection refused
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Pulling Pulling image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4"
kube-system replicaset-controller coredns-5d78c9869d SuccessfulDelete Deleted pod: coredns-5d78c9869d-wxj65
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-84985fb6b9-mwd4n Killing Stopping container cilium-operator
kube-system replicaset-controller cilium-operator-84985fb6b9 SuccessfulDelete Deleted pod: cilium-operator-84985fb6b9-mwd4n
kube-system default-scheduler coredns-6fccb86bcb-2l4xs Scheduled Successfully assigned kube-system/coredns-6fccb86bcb-2l4xs to ip-172-31-0-147.ec2.internal
kube-system deployment-controller cilium-operator ScalingReplicaSet Scaled up replica set cilium-operator-5d6bff587 to 1
kube-system default-scheduler cilium-operator-5d6bff587-7gnfz FailedScheduling 0/3 nodes are available: 3 node(s) didn't match pod anti-affinity rules. preemption: 0/3 nodes are available: 3 No preemption victims found for incoming pod..
kube-system deployment-controller coredns ScalingReplicaSet Scaled up replica set coredns-6fccb86bcb to 1
kube-system deployment-controller coredns ScalingReplicaSet Scaled up replica set coredns-6fccb86bcb to 2 from 1
kube-system deployment-controller cilium-operator ScalingReplicaSet Scaled down replica set cilium-operator-84985fb6b9 to 1 from 2
kube-system replicaset-controller cilium-operator-5d6bff587 SuccessfulCreate Created pod: cilium-operator-5d6bff587-7gnfz
kube-system default-scheduler coredns-6fccb86bcb-4z94v Scheduled Successfully assigned kube-system/coredns-6fccb86bcb-4z94v to ip-172-31-8-188.ec2.internal
kube-system default-scheduler cilium-operator-5d6bff587-l6vwk Scheduled Successfully assigned kube-system/cilium-operator-5d6bff587-l6vwk to ip-172-31-8-188.ec2.internal
kube-system replicaset-controller cilium-operator-5d6bff587 SuccessfulCreate Created pod: cilium-operator-5d6bff587-l6vwk
kube-system deployment-controller coredns ScalingReplicaSet Scaled down replica set coredns-5d78c9869d to 1 from 2
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-wxj65 Killing Stopping container coredns
kube-system replicaset-controller coredns-6fccb86bcb SuccessfulCreate Created pod: coredns-6fccb86bcb-2l4xs
kube-system replicaset-controller coredns-6fccb86bcb SuccessfulCreate Created pod: coredns-6fccb86bcb-4z94v
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Created Created container coredns
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Pulled Container image "registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v Created Created container coredns
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v Pulled Container image "registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v Started Started container coredns
kube-system default-scheduler cilium-operator-5d6bff587-7gnfz Scheduled Successfully assigned kube-system/cilium-operator-5d6bff587-7gnfz to ip-172-31-0-147.ec2.internal
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Unhealthy Readiness probe failed: Get "http://10.10.1.167:8181/ready": dial tcp 10.10.1.167:8181: connect: connection refused
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Started Started container coredns
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Created Created container cilium-operator
kube-system deployment-controller coredns ScalingReplicaSet Scaled down replica set coredns-5d78c9869d to 0 from 1
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-74hvm Killing Stopping container coredns
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz Pulled Container image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz Created Created container cilium-operator
kube-system replicaset-controller coredns-5d78c9869d SuccessfulDelete Deleted pod: coredns-5d78c9869d-74hvm
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz Started Started container cilium-operator
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Pulled Successfully pulled image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4" in 2.299092001s (2.299108707s including waiting)
kube-system deployment-controller cilium-operator ScalingReplicaSet Scaled down replica set cilium-operator-84985fb6b9 to 0 from 1
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-operator-84985fb6b9-26kqh Killing Stopping container cilium-operator
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Started Started container cilium-operator
kube-system replicaset-controller cilium-operator-84985fb6b9 SuccessfulDelete Deleted pod: cilium-operator-84985fb6b9-26kqh
(x2) kube-system kubelet ip-172-31-15-25.ec2.internal coredns-5d78c9869d-74hvm Unhealthy Readiness probe failed: Get "http://10.10.0.88:8181/ready": dial tcp 10.10.0.88:8181: connect: connection refused
(x22) kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v Unhealthy Readiness probe failed: HTTP probe failed with statuscode: 503
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeNotReady Node ip-172-31-8-188.ec2.internal status is now: NodeNotReady
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeAllocatableEnforced Updated Node Allocatable limit across pods
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal Rebooted Node ip-172-31-8-188.ec2.internal has been rebooted, boot id: 537cebc2-d021-4661-97f3-2acd2a74e78b
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasSufficientMemory Node ip-172-31-8-188.ec2.internal status is now: NodeHasSufficientMemory
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal InvalidDiskCapacity invalid capacity 0 on image filesystem
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal Starting Starting kubelet.
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasNoDiskPressure Node ip-172-31-8-188.ec2.internal status is now: NodeHasNoDiskPressure
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasSufficientPID Node ip-172-31-8-188.ec2.internal status is now: NodeHasSufficientPID
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container config
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Unhealthy Readiness probe failed: Get "http://127.0.0.1:9234/healthz": dial tcp 127.0.0.1:9234: connect: connection refused
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Pulled Container image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Created Created container cilium-operator
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Started Started container cilium-operator
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container config
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container mount-cgroup
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container apply-sysctl-overwrites
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container mount-cgroup
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container mount-bpf-fs
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container apply-sysctl-overwrites
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container clean-cilium-state
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container mount-bpf-fs
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container clean-cilium-state
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container install-cni-binaries
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container install-cni-binaries
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container cilium-agent
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container cilium-monitor
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container cilium-agent
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container cilium-monitor
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeReady Node ip-172-31-8-188.ec2.internal status is now: NodeReady
kube-system taint-controller coredns-6fccb86bcb-4z94v TaintManagerEviction Cancelling deletion of Pod kube-system/coredns-6fccb86bcb-4z94v
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal Starting Starting kubelet.
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal InvalidDiskCapacity invalid capacity 0 on image filesystem
default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeAllocatableEnforced Updated Node Allocatable limit across pods
default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal Starting Starting kubelet.
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeAllocatableEnforced Updated Node Allocatable limit across pods
default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal InvalidDiskCapacity invalid capacity 0 on image filesystem
kube-system kubelet ip-172-31-15-25.ec2.internal kube-controller-manager-ip-172-31-15-25.ec2.internal SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-15-25.ec2.internal kube-scheduler-ip-172-31-15-25.ec2.internal SandboxChanged Pod sandbox changed, it will be killed and re-created.
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal Starting Starting kubelet.
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeAllocatableEnforced Updated Node Allocatable limit across pods
(x7) default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasSufficientPID Node ip-172-31-15-25.ec2.internal status is now: NodeHasSufficientPID
(x7) default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasNoDiskPressure Node ip-172-31-15-25.ec2.internal status is now: NodeHasNoDiskPressure
(x8) default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal NodeHasSufficientMemory Node ip-172-31-15-25.ec2.internal status is now: NodeHasSufficientMemory
default kubelet ip-172-31-15-25.ec2.internal ip-172-31-15-25.ec2.internal InvalidDiskCapacity invalid capacity 0 on image filesystem
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal Created Created container kube-apiserver
kube-system kubelet ip-172-31-15-25.ec2.internal kube-scheduler-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/kube-scheduler:v1.27.3" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal etcd-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/etcd:3.5.7-0" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/kube-apiserver:v1.27.3" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal Started Started container kube-apiserver
kube-system kubelet ip-172-31-15-25.ec2.internal etcd-ip-172-31-15-25.ec2.internal Started Started container etcd
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-15-25.ec2.internal kube-scheduler-ip-172-31-15-25.ec2.internal Started Started container kube-scheduler
kube-system kubelet ip-172-31-15-25.ec2.internal kube-scheduler-ip-172-31-15-25.ec2.internal Created Created container kube-scheduler
kube-system kubelet ip-172-31-15-25.ec2.internal etcd-ip-172-31-15-25.ec2.internal SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-15-25.ec2.internal etcd-ip-172-31-15-25.ec2.internal Created Created container etcd
kube-system kubelet ip-172-31-15-25.ec2.internal kube-controller-manager-ip-172-31-15-25.ec2.internal Pulled Container image "registry.k8s.io/kube-controller-manager:v1.27.3" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal kube-controller-manager-ip-172-31-15-25.ec2.internal Created Created container kube-controller-manager
kube-system kubelet ip-172-31-15-25.ec2.internal kube-controller-manager-ip-172-31-15-25.ec2.internal Started Started container kube-controller-manager
(x6) default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeHasSufficientPID Node ip-172-31-0-147.ec2.internal status is now: NodeHasSufficientPID
(x6) default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeHasNoDiskPressure Node ip-172-31-0-147.ec2.internal status is now: NodeHasNoDiskPressure
(x6) default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal NodeHasSufficientMemory Node ip-172-31-0-147.ec2.internal status is now: NodeHasSufficientMemory
(x6) default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasSufficientPID Node ip-172-31-8-188.ec2.internal status is now: NodeHasSufficientPID
(x6) default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasNoDiskPressure Node ip-172-31-8-188.ec2.internal status is now: NodeHasNoDiskPressure
(x6) default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal NodeHasSufficientMemory Node ip-172-31-8-188.ec2.internal status is now: NodeHasSufficientMemory
default kubelet ip-172-31-8-188.ec2.internal ip-172-31-8-188.ec2.internal Rebooted Node ip-172-31-8-188.ec2.internal has been rebooted, boot id: 0f45d726-b7f5-4af2-bb89-73924315ca2a
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 FailedMount MountVolume.SetUp failed for volume "hubble-tls" : failed to sync secret cache: timed out waiting for the condition
default kubelet ip-172-31-0-147.ec2.internal ip-172-31-0-147.ec2.internal Rebooted Node ip-172-31-0-147.ec2.internal has been rebooted, boot id: e3040758-2e1d-4709-a52e-77cfdbbc314f
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Pulled Container image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz Unhealthy Readiness probe failed: Get "http://127.0.0.1:9234/healthz": dial tcp 127.0.0.1:9234: connect: connection refused
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container config
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container config
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 FailedMount MountVolume.SetUp failed for volume "kube-api-access-62j8x" : [failed to fetch token: serviceaccounts "cilium" is forbidden: User "system:node:ip-172-31-15-25.ec2.internal" cannot create resource "serviceaccounts/token" in API group "" in the namespace "kube-system": no relationship found between node 'ip-172-31-15-25.ec2.internal' and this object, failed to sync configmap cache: timed out waiting for the condition]
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-15-25.ec2.internal kube-apiserver-ip-172-31-15-25.ec2.internal Unhealthy Startup probe failed: HTTP probe failed with statuscode: 500
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Started Started container cilium-operator
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Created Created container cilium-operator
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz Started Started container cilium-operator
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 FailedMount MountVolume.SetUp failed for volume "clustermesh-secrets" : failed to sync secret cache: timed out waiting for the condition
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz Created Created container cilium-operator
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-operator-5d6bff587-7gnfz Pulled Container image "quay.io/cilium/operator-generic:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container config
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container config
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container config
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container mount-cgroup
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container config
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 SandboxChanged Pod sandbox changed, it will be killed and re-created.
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-operator-5d6bff587-l6vwk Unhealthy Readiness probe failed: Get "http://127.0.0.1:9234/healthz": dial tcp 127.0.0.1:9234: connect: connection refused
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container mount-cgroup
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container apply-sysctl-overwrites
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container mount-cgroup
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container mount-cgroup
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container mount-cgroup
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container apply-sysctl-overwrites
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container apply-sysctl-overwrites
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container apply-sysctl-overwrites
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container mount-bpf-fs
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container mount-bpf-fs
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container mount-cgroup
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container apply-sysctl-overwrites
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container apply-sysctl-overwrites
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container mount-bpf-fs
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container mount-bpf-fs
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container clean-cilium-state
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container clean-cilium-state
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container mount-bpf-fs
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container mount-bpf-fs
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container install-cni-binaries
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container clean-cilium-state
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container clean-cilium-state
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container install-cni-binaries
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container clean-cilium-state
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container clean-cilium-state
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container install-cni-binaries
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container install-cni-binaries
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container install-cni-binaries
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container cilium-monitor
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container cilium-monitor
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Started Started container cilium-agent
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container install-cni-binaries
kube-system kubelet ip-172-31-0-147.ec2.internal cilium-5qxnr Created Created container cilium-agent
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container cilium-monitor
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Started Started container cilium-agent
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Created Created container cilium-agent
kube-system kubelet ip-172-31-15-25.ec2.internal cilium-n9qs5 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Pulled Container image "quay.io/cilium/cilium:v1.14.0-snapshot.4" already present on machine
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Created Created container cilium-agent
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container cilium-agent
kube-system kubelet ip-172-31-8-188.ec2.internal cilium-htj82 Started Started container cilium-monitor
kube-system default-scheduler kube-scheduler LeaderElection ip-172-31-15-25.ec2.internal_c89cfd39-29e9-4558-8dac-19ad09ccd31e became leader
kube-system kube-controller-manager kube-controller-manager LeaderElection ip-172-31-15-25.ec2.internal_7b1989df-89cf-4e27-abeb-27b02a68bd70 became leader
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v Started Started container coredns
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Unhealthy Readiness probe failed: HTTP probe failed with statuscode: 503
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v Created Created container coredns
kube-system kubelet ip-172-31-8-188.ec2.internal coredns-6fccb86bcb-4z94v Pulled Container image "registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Killing Stopping container coredns
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Started Started container coredns
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Created Created container coredns
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Pulled Container image "registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
kube-system endpoint-controller kube-dns FailedToUpdateEndpoint Failed to update endpoint kube-system/kube-dns: Operation cannot be fulfilled on endpoints "kube-dns": the object has been modified; please apply your changes to the latest version and try again
default node-controller ip-172-31-0-147.ec2.internal RegisteredNode Node ip-172-31-0-147.ec2.internal event: Registered Node ip-172-31-0-147.ec2.internal in Controller
kube-system replicaset-controller coredns-6fccb86bcb SuccessfulCreate Created pod: coredns-6fccb86bcb-5n4bj
default node-controller ip-172-31-15-25.ec2.internal RegisteredNode Node ip-172-31-15-25.ec2.internal event: Registered Node ip-172-31-15-25.ec2.internal in Controller
default node-controller ip-172-31-8-188.ec2.internal RegisteredNode Node ip-172-31-8-188.ec2.internal event: Registered Node ip-172-31-8-188.ec2.internal in Controller
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-6fccb86bcb-5n4bj Pulled Container image "registry.k8s.io/coredns/coredns:v1.10.1" already present on machine
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-6fccb86bcb-5n4bj Started Started container coredns
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-6fccb86bcb-5n4bj Created Created container coredns
kube-system kubelet ip-172-31-15-25.ec2.internal coredns-6fccb86bcb-5n4bj Unhealthy Readiness probe failed: HTTP probe failed with statuscode: 503
kube-system kubelet ip-172-31-0-147.ec2.internal coredns-6fccb86bcb-2l4xs Unhealthy Readiness probe failed: Get "http://10.10.1.217:8181/ready": dial tcp 10.10.1.217:8181: connect: connection refused
default deployment-controller my-nginx ScalingReplicaSet Scaled up replica set my-nginx-646554d7fd to 1
default replicaset-controller my-nginx-646554d7fd SuccessfulCreate Created pod: my-nginx-646554d7fd-5llxc
default kubelet ip-172-31-0-147.ec2.internal my-nginx-646554d7fd-5llxc Started Started container my-nginx
default kubelet ip-172-31-0-147.ec2.internal my-nginx-646554d7fd-5llxc Created Created container my-nginx
default kubelet ip-172-31-0-147.ec2.internal my-nginx-646554d7fd-5llxc Pulled Successfully pulled image "nginx" in 180.445751ms (180.462038ms including waiting)
default kubelet ip-172-31-0-147.ec2.internal my-nginx-646554d7fd-5llxc Pulling Pulling image "nginx"