<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>故障排查 on jimyag's Blog</title><link>https://jimyag.com/blog/%E6%95%85%E9%9A%9C%E6%8E%92%E6%9F%A5/</link><description>jimyag 的个人博客，记录 Kubernetes、KubeVirt、Kube-OVN、Firecracker、Go 与云原生工程实践。</description><generator>Hugo</generator><language>zh-CN</language><copyright>Copyright © 2019, jimyag.</copyright><lastBuildDate>Mon, 21 Sep 2026 01:37:28 +0800</lastBuildDate><atom:link href="https://jimyag.com/blog/%E6%95%85%E9%9A%9C%E6%8E%92%E6%9F%A5/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Service 生产实践：DNS、连接排空与故障排查</title><link>https://jimyag.com/posts/kubernetes-service-production-practice/</link><pubDate>Mon, 21 Sep 2026 01:37:28 +0800</pubDate><guid>https://jimyag.com/posts/kubernetes-service-production-practice/</guid><description>从 CoreDNS、EndpointSlice 和 Pod 终止时间线出发，用真实故障注入解释 Service 解析成功但连接失败、滚动发布排空和分层排障。</description></item></channel></rss>