<?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 Solo</title><link>https://solo.hiero.org/tags/helm/</link><description>Recent content in Helm on Solo</description><generator>Hugo</generator><language>en</language><atom:link href="https://solo.hiero.org/tags/helm/index.xml" rel="self" type="application/rss+xml"/><item><title>Solo Helm Chart Cache</title><link>https://solo.hiero.org/docs/advanced-solo-setup/chart-cache/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://solo.hiero.org/docs/advanced-solo-setup/chart-cache/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A Solo network deployment installs a number of Helm charts (the Solo deployment
charts, mirror node, JSON-RPC relay, Explorer, block node, MinIO, Prometheus,
and the ingress controller). The &lt;strong&gt;chart cache&lt;/strong&gt; pre-pulls those chart tarballs
and stores them on disk, so deployments install them from the local cache
instead of fetching them from their chart repositories or OCI registries.&lt;/p&gt;
&lt;p&gt;The cache is used automatically: whenever Solo installs or upgrades a chart, it
first checks the cache for a tarball matching the exact chart name and version
being installed. On a match, the chart is installed from the local archive (no
network fetch); otherwise Solo falls back to the normal network install.&lt;/p&gt;</description></item></channel></rss>