<p>I want to spin up a single <strong>installer pod</strong> with <code>helm install</code> that once running, will apply some logic and install other applications into my cluster using <code>helm install</code>. </p>

<p>I'm aware of the helm dependencies, but I want to run some business logic with the installations and I'd rather do it in the <strong>installer pod</strong> and on the host triggering the whole installation process.</p>

<p>I found suggestions on using the Kubernetes REST API when inside a pod, but <code>helm</code> requires <code>kubectl</code> installed and configured.</p>

<p>Any ideas?</p>

<p>It seems this was a <strong>lot</strong> easier than I thought...</p>

<p>On a simple pod running Debian, I just <a href="https://kubernetes.io/docs/tasks/tools/install-kubectl/" rel="noreferrer">installed <strong>kubectl</strong></a>, and with the default service account's secret that's already mounted, the <strong>kubectl</strong> was already configured to the cluster's API.</p>

<p>Note that the configured default namespace is the one that my installer pod is deployed to.</p>

<p>Verified with</p>

<pre><code>$ kubectl cluster-info
$ kubectl get ns
</code></pre>

<p>I then <a href="https://docs.helm.sh/using_helm/#installing-helm" rel="noreferrer">installed <strong>helm</strong></a>, which was already using the <strong>kubectl</strong> to access the cluster for installing <strong>tiller</strong>.</p>

<p>Verified with</p>

<pre><code>$ helm version
$ helm init
</code></pre>

<p>I installed a test chart</p>

<pre><code>$ helm install --name my-release stable/wordpress
</code></pre>

<p><strong>It works!!</strong></p>

<p>I hope this helps</p>
