<p><strong>Issue itself</strong></p>
<p>Got an <strong>Azure Container registry</strong> as both image and chart storage. Assume it <code>myacr.azurecr.io</code> with 8 different charts pushed. As far as I read before Azure ACR is capable of storing charts and compatible with <strong>Helm 3</strong> (<strong>version 3.5.2</strong>).</p>
<p><a href="https://i.stack.imgur.com/EG7uU.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/EG7uU.png" alt="enter image description here" /></a>
The following steps to reproduce are simple.</p>
<ol start="0">
<li><code>helm repo add myacr https://myacr.azurecr.io/helm/v1/repo --username myusername -password admin123</code> - repo added. OK.</li>
<li><code>helm chart save ./my-chart/ myacr.azurecr.io/helm/my-chart:1.0.0</code> - chart saved. OK</li>
<li><code>helm push ./my-chart/ myacr.azurecr.io/helm/my-chart:1.0.0</code> - pushed. Available in Azure portal. OK.</li>
<li><code>helm repo update</code> - what could go wrong here? As expected. OK</li>
</ol>
<pre><code>Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the &quot;ingress-nginx&quot; chart repository
...Successfully got an update from the &quot;jetstack&quot; chart repository
...Successfully got an update from the &quot;myacr&quot; chart repository
Update Complete. ⎈Happy Helming!⎈
</code></pre>
<ol start="4">
<li><code>helm search repo -l</code> - I see everything from <code>ingress-nginx</code> and <code>jetstack</code> but nothing from <code>myacr</code> in the list.
Yet if I do <code>pull</code> and <code>export</code> everything works fine - chart is in place</li>
</ol>
<p><strong>What I tried</strong></p>
<ul>
<li>renaming repo name to helm/{app} according to some theories in the web - fail</li>
<li>reconfiguring chart with full descriptions e.t.c. according to <code>ingress-nginx</code> - fail</li>
<li>executing <code>helm search repo -l --devel</code> to see all possible chart versions - no luck</li>
<li>&quot;Swithing off and on again&quot; - removing and adding repo again with different combinations - fail</li>
<li>explicit slang language on every attempt - warms up a bit but doesn't solve the issue</li>
</ul>
<p><strong>The questions are</strong></p>
<ol>
<li>Is Azure ACR fully compatible with Helm 3?</li>
<li>Is there any specific workaround to make it compatible with Helm 3?</li>
<li>Does search functionality have any requirements to chart structure or version?</li>
</ol>

Artem Fomin
<blockquote>
<p>Is Azure ACR fully compatible with Helm 3?</p>
</blockquote>
<p>Yes, it's fully compatible with Helm 3.</p>
<blockquote>
<p>Is there any specific workaround to make it compatible with Helm 3?</p>
</blockquote>
<p>Nothing needs to be done because the first question is yes.</p>
<blockquote>
<p>Does search functionality have any requirements to chart structure or
version?</p>
</blockquote>
<p>You need to first to add the repo to your local helm with the command <code>az acr helm repo add --name myacr</code> or <code>helm repo add myacr https://myacr.azurecr.io/helm/v1/repo --username xxxxx --password xxxxxx</code>, and then you get the output like this running the command <code>helm search repo -l</code>:</p>
<p><a href="https://i.stack.imgur.com/R3h8R.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/R3h8R.png" alt="enter image description here" /></a></p>
<p>And the local repo looks like this:</p>
<p><a href="https://i.stack.imgur.com/Z8lzm.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Z8lzm.png" alt="enter image description here" /></a></p>
