<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Performance - Tag - Shengxu · Cloud Architecture &amp; DevOps</title><link>https://shengxu.pages.dev/en/tags/performance/</link><description>Cloud architecture &amp; DevOps notes by Shengxu: Kubernetes, Cilium, observability, LLM infra, AI agents.</description><generator>Hugo 0.153.2 &amp; FixIt v0.4.0-alpha.3-20251225101113-8ffb9a95</generator><language>en</language><lastBuildDate>Fri, 09 Jan 2026 14:00:00 +0800</lastBuildDate><atom:link href="https://shengxu.pages.dev/en/tags/performance/index.xml" rel="self" type="application/rss+xml"/><item><title>Farewell to iptables: The Nftables Revolution in Kubernetes Network Data Plane</title><link>https://shengxu.pages.dev/en/posts/kubernetes-nftables-revolution-2026/</link><pubDate>Fri, 09 Jan 2026 14:00:00 +0800</pubDate><guid>https://shengxu.pages.dev/en/posts/kubernetes-nftables-revolution-2026/</guid><category domain="https://shengxu.pages.dev/en/categories/kubernetes/">Kubernetes</category><description>&lt;p&gt;In the networking world of Kubernetes, &lt;code&gt;kube-proxy&lt;/code&gt; has long played the role of &amp;ldquo;gatekeeper,&amp;rdquo; responsible for distributing Service traffic to backend Pods. However, for years, we&amp;rsquo;ve endured the performance pain of iptables mode or been forced to migrate to the more complex IPVS mode.&lt;/p&gt;
&lt;p&gt;Fast forward to 2026, with &lt;strong&gt;Kubernetes 1.33 reaching General Availability (GA) in April 2025&lt;/strong&gt;, &lt;code&gt;nftables&lt;/code&gt; mode is no longer an experimental option—it has become the &amp;ldquo;new standard&amp;rdquo; for production environments. In fact, with the release of v1.35 at the end of 2025, the once-reliable &lt;code&gt;ipvs&lt;/code&gt; mode has been officially marked as &lt;strong&gt;Deprecated&lt;/strong&gt;. This marks a complete &amp;ldquo;return to fundamentals&amp;rdquo; for the Linux kernel network stack in the cloud-native era.&lt;/p&gt;</description></item></channel></rss>