Step-by-Step Guide to Upgrading a kubeadm Cluster from Kubernetes 1.35 to 1.36
Self-managed kubeadm clusters require manual upgrades, unlike managed services such as AKS, EKS, and GKE. The guide demonstrates a real upgrade of a three-node home lab cluster running Rocky Linux 10 on a single laptop with KVM. Kubeadm only permits upgrading one minor version at a time, so moving from 1.35 to 1.37 requires passing through 1.36 first. Each minor version hop involves a full drain-and-upgrade cycle repeated on every node, while patch-level upgrades within the same minor version can be skipped. The procedure is written for RPM-based distributions, with the same flow applying to Debian and Ubuntu using apt.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in