<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Upgrade :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/upgrade/index.html</link><description/><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0</copyright><lastBuildDate>Sun, 01 Nov 2026 14:00:00 +0100</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/upgrade/index.xml" rel="self" type="application/rss+xml"/><item><title>Upgrade a cluster with kubeadm</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/kubeadm-upgrade/index.html</link><pubDate>Sun, 01 Nov 2026 14:00:00 +0100</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/kubeadm-upgrade/index.html</guid><description>Author: Fabrice JAMMES (LinkedIn).
Objective Upgrade a kubeadm cluster from Kubernetes 1.36 to 1.37: the control plane first, then the worker Empty a node with kubectl drain before upgrading its kubelet Understand the version skew policy, which imposes this order The CKS curriculum lists “Upgrade Kubernetes to avoid vulnerabilities” in the Cluster Hardening domain: a security patch reaches a cluster only through an upgrade. The CKA curriculum lists the same task.</description></item></channel></rss>