<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Argo Rollouts on Todd's Builder Blog</title><link>https://todd.ekenstam.dev/tags/argo-rollouts/</link><description>Recent content in Argo Rollouts on Todd's Builder Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Todd Ekenstam</copyright><lastBuildDate>Mon, 24 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://todd.ekenstam.dev/tags/argo-rollouts/index.xml" rel="self" type="application/rss+xml"/><item><title>Operations, Done For You: Progressive Delivery and Debugging&lt;br&gt;&lt;small&gt;Simplifying Kubernetes, Part 3&lt;/small&gt;</title><link>https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-3/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0000</pubDate><guid>https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-3/</guid><description>&lt;p&gt;A service shouldn&amp;rsquo;t need a platform expert to get a canary, an analysis gate, and automatic rollback. IKS AIR treats operations as done-for-you: those best practices and guardrails are on by default, and progressive delivery with Argo Rollouts is how that shows up on every deploy.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-3/featured.jpg"/></item></channel></rss>