<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Hpa on The IT Hollow</title>
    <link>https://theithollow.com/tags/hpa/</link>
    <description>Recent content in Hpa on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 04 May 2020 14:05:00 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/hpa/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes Pod Auto-scaling</title>
      <link>https://theithollow.com/2020/05/04/kubernetes-pod-auto-scaling/</link>
      <pubDate>Mon, 04 May 2020 14:05:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/05/04/kubernetes-pod-auto-scaling/</guid>
      <description>&lt;p&gt;You&amp;rsquo;ve built your Kubernetes cluster(s). You&amp;rsquo;ve built your apps in containers. You&amp;rsquo;ve architected your services so that losing a single instance doesn&amp;rsquo;t cause an outage. And you&amp;rsquo;re ready for cloud scale. You deploy your application and are waiting to sit back and &amp;ldquo;profit.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;When your application spins up and starts taking on load, you are able to change the number of replicas to handle the additional load, but what about the promises of cloud and scaling? Wouldn&amp;rsquo;t it be better to deploy the application and let the platform scale the application automatically?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
