Kubelet logs: /var/log/kubelet.log

[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get http://localhost:10248/healthz: dial tcp 127.0.0.1:10248: connect: connection refused.

E1122 21:44:49.860990    2153 remote_runtime.go:334] "ContainerStatus from runtime service failed" err="rpc error: code = DeadlineExceeded desc = context deadline exceeded" containerID="54f47d9bd75961b31d996d3e1d01d366467750e8b2d9b21af2f528ed2eead846"

kubelet is posting ready status. AppArmor enabled

Related

• NodeHasDiskPressure
• EvictionThresholdMet
• NodeHasInsufficientMemory
• rebooted
• Started: Started container
• Killing: Stopping container
• Karpenter logs
• Kubernetes troubleshooting

See also

• kubelet, Pod Lifecycle Event Generator (PLEG), Kubelet conditions, /etc/kubernetes/kubelet.conf, /var/log/kubelet.log, Kubelet Container Runtime Interface (CRI), crictl, context deadline exceeded, E1122, E1124, Starting kubelet, NodeHasDiskPressure, NodeHasInsufficientMemory, rebooted, Node-pressure Eviction, Kubelet logs, manager: kubelet