<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HPA on ᕕ( ᐛ )ᕗ Jimyag&#39;s Blog</title>
    <link>https://jimyag.com/blog/hpa/</link>
    <description>专注于 Kubernetes、KubeVirt、OVN 和 Firecracker 的后端开发工程师</description>
    <generator>Hugo</generator>
    <language>zh-CN</language>
    <copyright>Copyright © 2019, jimyag.</copyright>
    <lastBuildDate>Tue, 08 Sep 2026 00:22:44 +0800</lastBuildDate>
    <atom:link href="https://jimyag.com/blog/hpa/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HPA 已经要求 4 个副本，为什么只有 1 个可用？</title>
      <link>https://jimyag.com/posts/hpa-tuning-troubleshooting/</link>
      <pubDate>Mon, 07 Sep 2026 23:24:22 +0800</pubDate>
      <guid>https://jimyag.com/posts/hpa-tuning-troubleshooting/</guid>
      <description>沿着指标、计算、策略、期望副本、调度与就绪链路，实测 HPA 稳定窗口、限速、多指标和常见故障。</description>
    </item>
    <item>
      <title>HPA 自定义指标：请求数不变，为什么副本会减半？</title>
      <link>https://jimyag.com/posts/hpa-application-throughput-metrics/</link>
      <pubDate>Mon, 07 Sep 2026 23:24:22 +0800</pubDate>
      <guid>https://jimyag.com/posts/hpa-application-throughput-metrics/</guid>
      <description>用一次请求数不变、请求体减半的实验，解释 Prometheus、Adapter 与 HPA 如何按应用内部的 RPS 和处理带宽扩缩容。</description>
    </item>
    <item>
      <title>队列已经空了，正在处理的任务能安全结束吗？</title>
      <link>https://jimyag.com/posts/hpa-queue-worker-autoscaling/</link>
      <pubDate>Mon, 07 Sep 2026 23:24:22 +0800</pubDate>
      <guid>https://jimyag.com/posts/hpa-queue-worker-autoscaling/</guid>
      <description>用真实任务的领取、处理与 ACK 实验，解释队列积压如何驱动 worker 扩缩容，以及缩容时如何避免丢失在途任务。</description>
    </item>
    <item>
      <title>HPA 入门：一个 CPU 指标如何让 Pod 从 1 个变成 4 个？</title>
      <link>https://jimyag.com/posts/hpa-cpu-autoscaling/</link>
      <pubDate>Sun, 06 Sep 2026 21:58:00 +0800</pubDate>
      <guid>https://jimyag.com/posts/hpa-cpu-autoscaling/</guid>
      <description>从一个 CPU 指标出发，用 kind 实测 Kubernetes HPA 如何计算副本数，并区分期望副本与真正可用的 Pod。</description>
    </item>
  </channel>
</rss>
