<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Blog on Kevin Jiang</title>
    <link>https://kevinjiang.dev/blog/</link>
    <description>Recent content in Blog on Kevin Jiang</description>
    <image>
      <title>Kevin Jiang</title>
      <url>https://kevinjiang.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://kevinjiang.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en</language>
    <lastBuildDate>Mon, 08 Dec 2025 10:30:14 -0500</lastBuildDate>
    <atom:link href="https://kevinjiang.dev/blog/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>KubeCon NA 2025 - Atlanta, GA</title>
      <link>https://kevinjiang.dev/blog/2025-12-08_kubecon/</link>
      <pubDate>Mon, 08 Dec 2025 10:30:14 -0500</pubDate>
      <guid>https://kevinjiang.dev/blog/2025-12-08_kubecon/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Last month, I had the opportunity to attend KubeCon North America 2025. The conference was packed with insightful sessions, technical deep-dives, and industry trends that are shaping the future of Kubernetes and cloud-native infrastructure. I wanted to share my personal highlights and key takeaways for anyone interested in the evolving landscape of cloud-native technologies.&lt;/p&gt;
&lt;h2 id=&#34;key-takeaways&#34;&gt;Key Takeaways&lt;/h2&gt;
&lt;h3 id=&#34;kubernetes-upgrade-rollbacks&#34;&gt;Kubernetes Upgrade Rollbacks&lt;/h3&gt;
&lt;p&gt;Upgrades remain one of the most critical and challenging aspects of Kubernetes operations. A recurring theme was the push for &lt;strong&gt;safer, more automated upgrade processes&lt;/strong&gt;. As of Kubernetes 1.32, upgrade rollbacks are now possible due to the introduction of the &amp;ldquo;compatibility version&amp;rdquo; concept.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
