https://robert.ludwick.us/tags/kubernetes/ Recent content in Kubernetes on Robert F.P. Ludwick Hugo en-us Tue, 18 Aug 2026 00:00:00 -0700 https://robert.ludwick.us/2026/08/18/fall-2026-kubernetes-upgrades/ Tue, 18 Aug 2026 00:00:00 -0700 https://robert.ludwick.us/2026/08/18/fall-2026-kubernetes-upgrades/ <h2 id="almost-annual-upgrades">Almost-Annual Upgrades</h2> <p>Every 10 months I run upgrades on my Kubernetes cluster. I haven&rsquo;t blogged about my cluster setup or hardware before; I set it all up pretty shortly after I wrapped up my <a href="https://robert.ludwick.us/2021/12/03/home-lab-network-evolution-part-5">home lab blog posts, part 5</a>. Maybe in the future I&rsquo;ll document my initial setup, but that&rsquo;s out of scope for this post.</p> <p>In this upgrade I needed to upgrade from <a href="https://kubernetes.io/blog/2025/04/23/kubernetes-v1-33-release/">1.33</a> all the way to <a href="https://kubernetes.io/blog/2026/04/22/kubernetes-v1-36-release/">1.36</a> - hitting <a href="https://kubernetes.io/blog/2025/08/27/kubernetes-v1-34-release/">1.34</a> and <a href="https://kubernetes.io/blog/2025/12/17/kubernetes-v1-35-release/">1.35</a> along the way. So I read through the upgrade documentation for 1.34 to 1.36&hellip; 1.34 itself was no concern, and neither was 1.36. But 1.35? It deprecated support for <a href="https://containerd.io/">containerd</a> versions less than <a href="https://containerd.io/docs/2.1/containerd-2.0/">2.0</a>. And I was running <a href="https://containerd.io/docs/1.7/">1.7</a> at the time.</p>