<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configuration on make me: APe</title><link>https://apealive.net/tags/configuration/</link><description>Recent content in Configuration on make me: APe</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2026 14:23:12 +0200</lastBuildDate><atom:link href="https://apealive.net/tags/configuration/index.xml" rel="self" type="application/rss+xml"/><item><title>CUE Configuration Kernel (Part 1/2)</title><link>https://apealive.net/post/cue-configuration-kernel-part-1/</link><pubDate>Mon, 27 Jul 2026 14:23:12 +0200</pubDate><guid>https://apealive.net/post/cue-configuration-kernel-part-1/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Subtitle: Mastering Declarative Configuration Options&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;p&gt;If you’ve spent any time operating Kubernetes in production, you’ve hit the Wall of YAML. Helm charts nested inside other Helm charts, Kustomize overlays overriding overlays, and a sea of copy-pasted boilerplate that slowly drifts across dev, staging, and production environments.&lt;/p&gt;
&lt;p&gt;Most platform engineering teams try to solve this with more template processing, leading to the infamous &amp;quot;Kubernetes configuration tax&amp;quot; where engineers spend more time writing string-replacement logic than writing core application code.&lt;/p&gt;</description></item></channel></rss>