<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Edge Computing</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Edge Computing feed</description>
    <item>
      <title>Article: Proactive Autoscaling for Edge Applications in Kubernetes</title>
      <link>https://www.infoq.com/articles/proactive-autoscaling-edge-kubernetes/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Edge+Computing</link>
      <description>&lt;img src="https://res.infoq.com/articles/proactive-autoscaling-edge-kubernetes/en/headerimage/proactive-autoscaling-edge-kubernetes-header-1770721062673.jpg"/&gt;&lt;p&gt;Kubernetes often reacts too late when traffic suddenly increases at the edge. A proactive scaling approach that considers response time, spare CPU capacity, and container startup delays can add or remove instances more smoothly, prevent sudden spikes, and keep performance stable on systems with limited resources.&lt;/p&gt; &lt;i&gt;By Rajeev Kallayil Ravi&lt;/i&gt;</description>
      <category>Kubernetes Operator</category>
      <category>Performance &amp; Scalability</category>
      <category>Kubernetes</category>
      <category>Site Reliability Engineering</category>
      <category>Edge Computing</category>
      <category>Cloud Native Architecture</category>
      <category>Observability</category>
      <category>Platform Engineering</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Tue, 17 Feb 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/proactive-autoscaling-edge-kubernetes/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Edge+Computing</guid>
      <dc:creator>Rajeev Kallayil Ravi</dc:creator>
      <dc:date>2026-02-17T09:00:00Z</dc:date>
      <dc:identifier>/articles/proactive-autoscaling-edge-kubernetes/en</dc:identifier>
    </item>
  </channel>
</rss>
