<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Upgrades on Support Tools</title><link>https://support.tools/categories/upgrades/</link><description>Recent content in Upgrades on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 25 Oct 2024 14:30:00 -0500</lastBuildDate><atom:link href="https://support.tools/categories/upgrades/index.xml" rel="self" type="application/rss+xml"/><item><title>The Importance of Sequential Kubernetes Version Upgrades</title><link>https://support.tools/kubernetes-sequential-upgrades/</link><pubDate>Fri, 25 Oct 2024 14:30:00 -0500</pubDate><guid>https://support.tools/kubernetes-sequential-upgrades/</guid><description>&lt;p&gt;Upgrading Kubernetes clusters requires careful planning. While &lt;strong&gt;skipping versions&lt;/strong&gt; (e.g., going from 1.28 to 1.30) may seem tempting, it can introduce unexpected issues. This post explains &lt;strong&gt;why sequential upgrades&lt;/strong&gt; (1.28 → 1.29 → 1.30) are essential and offers tips for &lt;strong&gt;safe upgrade paths&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="why-sequential-upgrades-matter"&gt;Why Sequential Upgrades Matter&lt;/h2&gt;&#10;&lt;p&gt;Kubernetes releases new minor versions approximately every &lt;strong&gt;three months&lt;/strong&gt;, and each version contains &lt;strong&gt;new features, bug fixes, and deprecations&lt;/strong&gt;. Skipping versions may create:&lt;/p&gt;</description></item></channel></rss>