<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Service on jimyag's Blog</title><link>https://jimyag.com/blog/service/</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/service/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><item><title>Kubernetes Service 的数据面实现：iptables、nftables 与 eBPF</title><link>https://jimyag.com/posts/kubernetes-service-dataplane/</link><pubDate>Mon, 21 Sep 2026 01:27:12 +0800</pubDate><guid>https://jimyag.com/posts/kubernetes-service-dataplane/</guid><description>用同一组 kind Service 实验比较 kube-proxy 的 iptables、nftables、IPVS 模式，以及 Cilium、Calico 的 eBPF kube-proxy replacement。</description></item><item><title>Kubernetes Service 的流量路径：kube-proxy、NAT 与源 IP</title><link>https://jimyag.com/posts/kubernetes-service-traffic-path/</link><pubDate>Mon, 21 Sep 2026 01:01:40 +0800</pubDate><guid>https://jimyag.com/posts/kubernetes-service-traffic-path/</guid><description>从数据包五元组出发，结合 kind、kube-proxy 源码、iptables 规则和服务端日志，解释 ClusterIP、NodePort、DNAT、SNAT 与客户端源 IP 的真实流转。</description></item><item><title>Kubernetes Service：从稳定入口到服务发现</title><link>https://jimyag.com/posts/kubernetes-service-networking/</link><pubDate>Sat, 19 Sep 2026 20:35:12 +0800</pubDate><guid>https://jimyag.com/posts/kubernetes-service-networking/</guid><description>解释 Service 如何通过 EndpointSlice 维护后端，并比较四种 Service type、Headless 服务发现和常见排查路径。</description></item></channel></rss>