<p>We use <code>helm</code> to manage our <code>kubernetes applications</code>.
We use kubectl commands like this :
<code>kubectl --token $TOKEN get pods</code></p>

<p>So we use token based authentication system to run <code>kubectl</code> as opposed to auth info stored at <code>~/.kube/config</code> file.</p>

<p>Now problem is : We are not able to run any of helm commands as all helm commands throw : <code>Error: Unauthorized</code>.</p>

<p>So question is how to use helm with token based authentication system.</p>

<p>Context :
Recently our DevOps team moved from <code>self managed K8S</code> to amazon's EKS. Only mechanism they provided to authenticate kubectl is through token.</p>

<p>Currently Helm does not support Token based authorization mechanism with Kubernetes API. Therefore, there is no option for user-provided bearer token verification.You can find Github <a href="https://github.com/helm/helm/issues/1918" rel="nofollow noreferrer">issue</a> with a proposal of Authentication and Authorization support in Tiller.</p>

<p>Helm 3 Design <a href="https://github.com/helm/community/blob/master/helm-v3/000-helm-v3.md" rel="nofollow noreferrer">Proposal</a>  has been announced with a significant changes to be implemented such as the new Security <a href="https://github.com/helm/community/blob/master/helm-v3/007-security.md" rel="nofollow noreferrer">concepts</a> .</p>
