<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>网络优化 on 知识铺的博客</title>
    <link>https://index.zshipu.com/geek001/tags/%E7%BD%91%E7%BB%9C%E4%BC%98%E5%8C%96/</link>
    <description>Recent content in 网络优化 on 知识铺的博客</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://index.zshipu.com/geek001/tags/%E7%BD%91%E7%BB%9C%E4%BC%98%E5%8C%96/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pod重启后请求消失：Kubernetes生产网络的真实陷阱</title>
      <link>https://index.zshipu.com/geek001/post/20260904/Pod%E9%87%8D%E5%90%AF%E5%90%8E%E8%AF%B7%E6%B1%82%E6%B6%88%E5%A4%B1Kubernetes%E7%94%9F%E4%BA%A7%E7%BD%91%E7%BB%9C%E7%9A%84%E7%9C%9F%E5%AE%9E%E9%99%B7%E9%98%B1/</link>
      <pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://index.zshipu.com/geek001/post/20260904/Pod%E9%87%8D%E5%90%AF%E5%90%8E%E8%AF%B7%E6%B1%82%E6%B6%88%E5%A4%B1Kubernetes%E7%94%9F%E4%BA%A7%E7%BD%91%E7%BB%9C%E7%9A%84%E7%9C%9F%E5%AE%9E%E9%99%B7%E9%98%B1/</guid>
      <description>Pod重启直接切断服务发现链路 当微服务集群规模扩大后，Pod频繁重启成为常态。每次重启，Pod的IP地址都会变化，而许多服务发现机制依赖于这些IP或依赖于未及时更新的Endpoints。结果是请求直接发往已不存在的地址，客户端收到连接拒绝或超时错误。 在管理大规模微服务时，这种情况</description>
    </item>
  </channel>
</rss>
