SSH, which stands for Secure Shell, is a network protocol that allows users to operate computers and servers over the Internet. It provides a secure channel over a very unsecured network. SSH uses encryption to ensure that the traffic between two connected devices can not be interpreted.

A couple posts ago, we saw how signals are handled by applications, containers and pods and how this is affected by container specific details. With this post as a starting point, I went down the rabbit hole of Bash shell commands, processes and signals.

When shutting down an application, a container or a pod, we want it to happen smoothly, all serving requests to be completed and resources to be properly released. For this to happen, we need the signal to be propagated from the source (pod, container, OS) to the application.

Disclaimer: This blog post is my notes and interpretation on concepts and ideas presented in the book together with some personal reflections from my personal experience and career.