<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Knative on Panditha</title>
    <link>https://panditha.com/tags/knative/</link>
    <description>Recent content in Knative on Panditha</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 09 Mar 2026 09:53:20 +1100</lastBuildDate>
    <atom:link href="https://panditha.com/tags/knative/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Knative Scale to Zero: Running Low-Traffic Services Efficiently</title>
      <link>https://panditha.com/posts/knative-serve-scale-to-zero/</link>
      <pubDate>Mon, 09 Mar 2026 09:53:20 +1100</pubDate>
      <guid>https://panditha.com/posts/knative-serve-scale-to-zero/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://knative.dev/docs/serving/&#34;&gt;Knative Serving&lt;/a&gt; provides a simple way to run HTTP workloads on Kubernetes that automatically scale based on traffic. One of the most useful capabilities is scale to zero. When a service receives no traffic, the pods disappear completely. When a request arrives, Knative starts the workload again and routes the request to it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;motivation&#34;&gt;Motivation&lt;/h2&gt;&#xA;&lt;p&gt;Recently, I discussed this problem with a friend who hosts many small client services on a public cloud platform. These services are used infrequently, some only a few times per month, yet they incur continuous hosting charges. He wanted to reduce costs without sacrificing flexibility. Moving everything back to on-premises hardware seemed like an option, but it would sacrifice the ability to scale globally or easily migrate back to the cloud. Knative with scale-to-zero offers a middle ground: run a small platform at home, host services that consume resources only when actually invoked, and maintain the option to move workloads back to public cloud infrastructure if needs change. For anyone managing many lightweight internal services, especially those used infrequently, this pattern can dramatically reduce infrastructure costs while preserving operational flexibility.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
