<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pod Sizing on Todd's Builder Blog</title><link>https://todd.ekenstam.dev/tags/pod-sizing/</link><description>Recent content in Pod Sizing on Todd's Builder Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Todd Ekenstam. Opinions expressed here are my own and not those of my employer.</copyright><lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://todd.ekenstam.dev/tags/pod-sizing/index.xml" rel="self" type="application/rss+xml"/><item><title>AI-Powered Autoscaling: How the Platform Sizes a Service&lt;br&gt;&lt;small&gt;Simplifying Kubernetes, Part 2&lt;/small&gt;</title><link>https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-2/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate><guid>https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-2/</guid><description>&lt;p&gt;Load tests can be automated. Completing the analysis and reflecting the findings into HPA and CPU/memory requests is the part that usually happens once at launch and then rarely again. IKS AIR fixes that with AIR Managed Autoscaling: it sizes each service continuously from real traffic instead of a guess.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-2/featured.jpg"/></item></channel></rss>