<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kubernetes on Technology Enlightened</title>
    <link>https://pprakash.me/tags/kubernetes/</link>
    <description>Recent content in Kubernetes on Technology Enlightened</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>&amp;copy; &lt;a href=&#34;https://github.com/p-prakash/&#34;&gt;Prakash P&lt;/a&gt; 2015 - 2023</copyright>
    <lastBuildDate>Mon, 27 Feb 2023 08:00:00 +0100</lastBuildDate>
    <atom:link href="https://pprakash.me/tags/kubernetes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Optimize Azure Kubernetes Service Node Cost by Combining OnDemand and Spot VMs</title>
      <link>https://pprakash.me/tech/2023/02/27/optimize-aks-node-cost-by-combining-spot-ondemand-vms/</link>
      <pubDate>Mon, 27 Feb 2023 08:00:00 +0100</pubDate>
      <guid>https://pprakash.me/tech/2023/02/27/optimize-aks-node-cost-by-combining-spot-ondemand-vms/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;While it&amp;rsquo;s possible to run the kubernetes nodes either in on-demand or spot node pools separately. We can optimize the application cost without compromising the reliability by placing the pods unevenly on spot and OnDemand VMs using the &lt;strong&gt;&lt;a href=&#34;https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/&#34;&gt;topology spread constraints&lt;/a&gt;&lt;/strong&gt;. With baseline amount of pods deployed in OnDemand node pool offering reliability we can scale on spot node pool based on the load at a lower cost. In this post, we will go through step by step approach on deploying an application spread unevenly on spot and OnDemand VMs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
