http://elposhox.dev/en/tags/starlark/Recent content in Starlark on El PoshoXHugo -- gohugo.ioen© 2026 Az García ZúñigaSat, 20 Jun 2026 00:00:00 +0000http://elposhox.dev/en/posts/oci-config-artifacts-kargo/Sat, 20 Jun 2026 00:00:00 +0000http://elposhox.dev/en/posts/oci-config-artifacts-kargo/<h1 class="relative group">Compiled Config as an OCI Artifact: Atomicity in Production with Kargo <div id="compiled-config-as-an-oci-artifact-atomicity-in-production-with-kargo" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#compiled-config-as-an-oci-artifact-atomicity-in-production-with-kargo" aria-label="Anchor">#</a> </span> </h1> <div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"> The complete problem of auto-sync + atomicity + multi-region. The five alternatives I evaluated. The solution with OCI artifacts. The complete PromotionTask. The test results. And why your compiled config deserves the same treatment as your Docker image. </div> <p>I&rsquo;ve spent weeks solving a problem that seemed simple and ended up being a redesign of how compiled config reaches production. The short version: auto-sync in production + config as a file in git + multiple regions = a ticking time bomb. Here&rsquo;s everything I tried, what I discarded, and what became an ADR.</p>