https://slnotes.blog.castrillon.ch/k8s/operations/Recent content in Operations on SL NotebookHugo -- gohugo.ioThu, 01 Oct 2026 15:00:06 +0200https://slnotes.blog.castrillon.ch/k8s/operations/backup/Thu, 01 Oct 2026 15:00:06 +0200https://slnotes.blog.castrillon.ch/k8s/operations/backup/There a several options to backup the running configuration and workload of a cluster. Some are listed below: Declarative Resources in Git The simplest way of backing up configurations is making sure to always deploy everything via declarative approach (YAML files) and storing these files in version control (e.g github). This is a way to ensure that even on complete cluster failure, all workloads can be restored with the exact same config as before.https://slnotes.blog.castrillon.ch/k8s/operations/cluster_up/Tue, 15 Sep 2026 17:01:53 +0200https://slnotes.blog.castrillon.ch/k8s/operations/cluster_up/Kubernetes, and all the components that integrate it, need to be updated regularly to keep up with bug fixes, new features and security fixes. Versioning and when to update K8s components can work with different versions, however there are some rules: Nothing can have a higher version than the API Server Controller manager and scheduler can be one minor version below Kubelet and kubeproxy can be up to 3 minor versions below Kubectl can be between 1 below and 1 over In the same way, only the 3 latest minor releases are officially supported by k8s at any time.https://slnotes.blog.castrillon.ch/k8s/operations/draining/Mon, 14 Sep 2026 17:02:30 +0200https://slnotes.blog.castrillon.ch/k8s/operations/draining/Sometimes, the underlying k8s nodes need to be restarted or maintaned. In this cases, workloads running in the node will be handled by k8s in the following way: If the node is “down” for less than 5 min, the pods will be restarted in the same node. This time is configurable as pod eviction timeout. If it lasts more than that, pods are terminated (dead). If they are part of a replica set they will be replicated on other node.