<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Requests on PlumePHP</title><link>https://plumephp.com/tags/requests/</link><description>Recent content in Requests on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sun, 27 Sep 2026 13:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/requests/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes 资源限制与 QoS：requests/limits 的工程化实践</title><link>https://plumephp.com/kubernetes-resource-limits-qos/</link><pubDate>Sun, 27 Sep 2026 13:00:00 +0800</pubDate><guid>https://plumephp.com/kubernetes-resource-limits-qos/</guid><description>&lt;p&gt;资源管理是 Kubernetes 里&lt;strong&gt;最容易被低估、却直接影响稳定性与账单&lt;/strong&gt;的配置。写错 requests/limits，轻则 Pod 被驱逐、服务抖动，重则节点被打爆、集群雪崩。本指南从 &lt;strong&gt;requests/limits 的语义&lt;/strong&gt; 到 &lt;strong&gt;QoS 分级&lt;/strong&gt; 再到 &lt;strong&gt;配额治理与驱逐机制&lt;/strong&gt;，帮你建立一套既不过度配置、也不资源超卖的资源工程体系。&lt;/p&gt;</description></item></channel></rss>