What is a disruption the action of preventing something, especially a system, process, or event, from continuing as usual or as expected. – https://dictionary.cambridge.org/de/worterbuch/englisch/disruption Kubernetes differentiates between 2 kinds of disruptions: involuntary (Outside the control of Kubernetes) hardware failure kernel panic etc. voluntary (controlled using Kubernetes mechanisms) draining a node (repair, upgrade, scale down) priority based eviction (to allow other, high priority pods to be scheduled instead) Deployment,StatefulSet,DaemonSet, etc. update deleting a pod Kubernetes will try to move pods from unhealthy to healthy nodes when encountering involuntary disruptions. Read more...

Note This article only talks about the kubelet + CRI based container runtimes. Pre-CRI based implementations (i.e., Docker) are slightly different. Logging & Kubernetes Logs can provide helpful insights into an application. Especially when troubleshooting bugs, logs can help us understand the why? In Kubernetes, logs from containers are being handled by the container-runtime (e.g. containerd, cri-o, etc.) & the kubelet, as long as containers write logs to stdout or stderr. Read more...