<p>Helm offers the option of listing <a href="https://helm.sh/docs/helm/helm_dependency_list/" rel="nofollow noreferrer">dependencies</a> for a chart when browsing through its files.</p>
<p>So if I am above the folder of <code>my-chart</code>, I can perform</p>
<pre><code>▶ helm dependency list my-chart
NAME    VERSION REPOSITORY          STATUS
common  0.12.6  file://../common/   ok
</code></pre>
<p>How can I get the dependencies for the <strong>INSTALLED</strong> chart, i.e. by retrieving this info from the actualy deployed version? (i.e. the one running on my cluster)</p>

pkaramol
<p>No, you can retrieve this information only using documentation you provided. You should:</p>
<ul>
<li>Download the chart with <code>$ helm pull repo/name --untar</code> (skip this if you already have it)</li>
<li>Go inside the chart directory</li>
<li>Invoke command: <code>$ helm dependency list my-chart</code></li>
</ul>
<p>Alternatively you can inspect <a href="https://kb.novaordis.com/index.php/Helm_Chart_requirements.yaml" rel="noreferrer">requirements.yaml</a> for helm2 or <a href="https://kb.novaordis.com/index.php/Helm_Chart_Chart.yaml#dependencies" rel="noreferrer">Chart.yaml</a> for helm3, but you will find there only transitive dependencies :</p>
<blockquote>
<p>All applications, maybe with the exception of the most trivial,
usually depend on other runtime components, such as web servers,
caches, databases, etc. Helm supports modularization via a dependency
mechanism, which allows to formally specify, manage and deploy
dependencies as part of a Helm release. A Helm chart may declare
dependencies, which are other Helm charts published in external
repositories, conveniently packaged by people who presumably know the
respective components well. The simples possible example is a chart A
-- the dependent - that declared its reliance on a chart B - the dependency - by specifying chart B's “coordinates” (name, version and
repository URL) as part of its own metadata. The exact way in which
the dependencies are declared has evolved across Helm releases. For
Helm 2 charts, the dependencies are declared in a dedicated
requirements.yaml file, while for Helm 3 chart, the dependencies are
declared as part of the chart manifest Chart.yaml. However, the way
the dependencies are processed during installation has remained the
same.</p>
</blockquote>
<p>Good article: <a href="https://kb.novaordis.com/index.php/Helm_Dependencies" rel="noreferrer">Helm Dependencies</a></p>
