<?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>Kubernetes on Zhao Xue</title><link>https://xuezhaojun.github.io/tags/kubernetes/</link><description>Recent content in Kubernetes on Zhao Xue</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://xuezhaojun.github.io/tags/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>从一次 K8s Controller OOM 聊起：彻底搞懂 Go GMP 调度模型</title><link>https://xuezhaojun.github.io/collections/go-concurrency/go-goroutine-gmp/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://xuezhaojun.github.io/collections/go-concurrency/go-goroutine-gmp/</guid><description>不讲干巴巴的八股文。从一个真实的 Kubernetes controller 内存暴涨 + 延迟飙高的线上事故出发，用 pprof 数据倒推 GMP 调度模型的每个概念，让你理解为什么要学这些东西。</description></item><item><title>从一次 K8s Webhook 超时聊起：彻底搞懂 Go Channel 底层原理</title><link>https://xuezhaojun.github.io/collections/go-concurrency/go-channel/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://xuezhaojun.github.io/collections/go-concurrency/go-channel/</guid><description>一个 K8s admission webhook 在高峰期频繁超时，但单个请求处理逻辑明明很快。问题出在 channel 的使用方式上。从这个事故出发，拆解 channel 的底层结构、发送接收流程、select 实现，以及那些年我们踩过的 channel 坑。</description></item></channel></rss>