<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevOps - Tag - Shengxu · Cloud Architecture &amp; DevOps</title><link>https://shengxu.pages.dev/en/tags/devops/</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>Sat, 24 Jan 2026 12:47:00 +0800</lastBuildDate><atom:link href="https://shengxu.pages.dev/en/tags/devops/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Complexity: Starting from a Job Interview Question</title><link>https://shengxu.pages.dev/en/posts/kubernetes-complexity-interview/</link><pubDate>Sat, 24 Jan 2026 12:47:00 +0800</pubDate><guid>https://shengxu.pages.dev/en/posts/kubernetes-complexity-interview/</guid><category domain="https://shengxu.pages.dev/en/categories/kubernetes/">Kubernetes</category><category domain="https://shengxu.pages.dev/en/categories/devops/">DevOps</category><description>&lt;p&gt;I recently went through a job interview where the interviewer posed a seemingly routine question: &amp;ldquo;In your opinion, when should you use Kubernetes, and when is it unnecessary and just adds complexity?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;I answered it fairly smoothly at the time, but the question lingered in my mind long afterward. What made it so &amp;ldquo;sharp&amp;rdquo; was that it stepped beyond the technical details of &amp;ldquo;how to use K8s&amp;rdquo; and cut straight to the core trade-off in architecture design: Are we introducing a tech stack to solve a real business pain point, or just to satisfy the team&amp;rsquo;s &amp;ldquo;anxiety about being cutting-edge&amp;rdquo;?&lt;/p&gt;</description></item><item><title>Helm 4 Deep Dive: More Than a Version Bump – A New Beginning for the Kubernetes-Native Era</title><link>https://shengxu.pages.dev/en/posts/helm-4-deep-dive-kubernetes-native-delivery/</link><pubDate>Thu, 22 Jan 2026 10:00:00 +0800</pubDate><guid>https://shengxu.pages.dev/en/posts/helm-4-deep-dive-kubernetes-native-delivery/</guid><category domain="https://shengxu.pages.dev/en/categories/kubernetes/">Kubernetes</category><category domain="https://shengxu.pages.dev/en/categories/devops/">DevOps</category><description>&lt;p&gt;In the infrastructure world, some version updates are &amp;ldquo;icing on the cake,&amp;rdquo; while others are &amp;ldquo;transformative.&amp;rdquo; If Helm 3 freed us from the nightmare of Tiller, then &lt;strong&gt;Helm 4&lt;/strong&gt;, officially released in &lt;strong&gt;November 2025&lt;/strong&gt;, marks the coming-of-age moment when Helm truly understood and embraced Kubernetes&amp;rsquo; declarative philosophy.&lt;/p&gt;
&lt;p&gt;After two months of community validation and official documentation refinement, this article will clarify the easily misunderstood technical details based on Helm 4&amp;rsquo;s actual release state.&lt;/p&gt;</description></item></channel></rss>