<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Helm on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/helm/</link>
    <description>Recent content in Helm on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 23 Apr 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/helm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ChartMuseum vs Harbor vs OCI: Self-Hosted Helm Chart Repositories 2026</title>
      <link>https://www.pistack.xyz/posts/chartmuseum-vs-harbor-vs-oci-self-hosted-helm-chart-repositories-2026/</link>
      <pubDate>Thu, 23 Apr 2026 09:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/chartmuseum-vs-harbor-vs-oci-self-hosted-helm-chart-repositories-2026/</guid>
      <description>&lt;h2 id=&#34;why-self-host-helm-chart-repositories&#34;&gt;Why Self-Host Helm Chart Repositories&lt;/h2&gt;&#xA;&lt;p&gt;Helm is the de facto package manager for Kubernetes, with over 29,700 stars on GitHub as of April 2026. Every Helm deployment depends on charts — but where do those charts live? Public repositories like &lt;code&gt;artifacthub.io&lt;/code&gt; work for open-source charts, but organizations running internal applications need private, self-hosted chart repositories.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
