<p>Prior to Helm 3, it was possible to associate a service account in helm initialization via</p>

<pre><code>helm init --service-account tiller
</code></pre>

<p>But since <code>helm init</code> is now deprecated, how can we find out which service account is the Helm associated with?  </p>

Farshid
<p>Helm 3 will have the same permissions according to the default config in <code>~/.kube/config</code> or another config if specified in your system environment variable <code>$KUBECONFIG</code> or overridden using the following command options</p>
<pre><code>      --kube-context string              name of the kubeconfig context to use
      --kubeconfig string                path to the kubeconfig file
</code></pre>
<blockquote>
<p>With Tiller gone, the security model for Helm is radically simplified. Helm 3 now supports all the modern security, identity, and authorization features of modern Kubernetes. Helm’s permissions are evaluated using your <code>kubeconfig</code> file. Cluster administrators can restrict user permissions at whatever granularity they see fit. — <a href="https://helm.sh/docs/faq/#removal-of-tiller" rel="nofollow noreferrer">Changes since Helm 2: Removal of Tiller</a></p>
</blockquote>
