Hacker News Reader

It doesn't. The usual approach is to create new nodes with the updated OS, migrate all workloads over and then throw away the old ones

Your cluster consists of multiple machines ('nodes'). Upgrading is as simple as adding a new, upgraded node, then evicting everything from one of the existing nodes, then take it down. Repeat until every node is replaced.

Downtime is the same as with a deploment, so if you run at least 2 copies of everything there should be no downtime.

As for updating the images of your containers, you build them again with the newer base image, then deploy.

Are you talking about upgrades of the host OS or the base of the image? I think you are talking about the latter. Others covered updating the host.

Upgrades of the Docker image are done by pushing a new image, and updating the Deployment to use the new image, and applying it. Kubernetes will start new containers for the new image, and when they are running, kill off the old containers. There should be no interruption. It isn't any different than normal deploy.