<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kustomize on Todd's Builder Blog</title><link>https://todd.ekenstam.dev/tags/kustomize/</link><description>Recent content in Kustomize 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>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://todd.ekenstam.dev/tags/kustomize/index.xml" rel="self" type="application/rss+xml"/><item><title>The Developer Experience Problem with Kubernetes at Scale&lt;br&gt;&lt;small&gt;Simplifying Kubernetes, Part 1&lt;/small&gt;</title><link>https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-1/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-1/</guid><description>&lt;p&gt;At Intuit we run thousands of production services across hundreds of Kubernetes clusters. At that scale, developers were spending 30-40% of their time on YAML, deploys, and ops (the outer loop) instead of writing product code.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://todd.ekenstam.dev/posts/202608-simplifying-kubernetes-part-1/featured.jpg"/></item></channel></rss>