<?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 DevOps &amp; Rock&#39;N&#39;Roll</title>
    <link>https://artazar.pages.dev/tags/kustomize/</link>
    <description>Recent content in Kustomize on DevOps &amp; Rock&#39;N&#39;Roll</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 19 Aug 2026 15:55:02 +0700</lastBuildDate>
    <atom:link href="https://artazar.pages.dev/tags/kustomize/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A FluxCD repo layout that survives forty applications</title>
      <link>https://artazar.pages.dev/blog/08-fluxcd-repo-layout/</link>
      <pubDate>Tue, 05 May 2026 00:08:30 +0000</pubDate>
      <guid>https://artazar.pages.dev/blog/08-fluxcd-repo-layout/</guid>
      <description>&lt;p&gt;Every GitOps repository starts beautiful. One cluster, five apps, a flat &lt;code&gt;apps/&lt;/code&gt; directory, and a Kustomization that reconciles the lot. Then the second cluster appears. Then staging needs a different replica count. Then somebody needs their own namespace with their own RBAC and no access to anyone else&amp;rsquo;s. Six months later you are grepping through forty &lt;code&gt;kustomization.yaml&lt;/code&gt; files trying to work out why a change to a shared ConfigMap took down two environments.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
