<p>I have just created a GKE cluster on Google Cloud platform. I have installed in the cloud console <code>helm</code> :</p>

<pre><code>$ helm version
version.BuildInfo{Version:"v3.0.0", GitCommit:"e29ce2a54e96cd02ccfce88bee4f58bb6e2a28b6", GitTreeState:"clean", GoVersion:"go1.13.4"}

</code></pre>

<p>I have also created the necessary <code>serviceaccount</code> and <code>clusterrolebinding</code> objects:</p>

<pre><code>$ cat helm-rbac.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  name: tiller
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: tiller
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
  - kind: ServiceAccount
    name: tiller
    namespace: kube-system


$ kubectl apply -f helm-rbac.yaml                                                                    

serviceaccount/tiller created
clusterrolebinding.rbac.authorization.k8s.io/tiller created
</code></pre>

<p>However trying to initialise <code>tiller</code> gives me the following error:</p>

<pre><code>$ helm init --service-account tiller --history-max 300
Error: unknown flag: --service-account
</code></pre>

<p>Why is that?</p>

pkaramol
<blockquote>
<p>However trying to initialise tiller gives me the following error:</p>
<p>Error: unknown flag: --service-account</p>
<p>Why is that?</p>
</blockquote>
<p><a href="https://helm.sh/blog/helm-3-released/" rel="noreferrer">Helm <strong>3</strong> is a major upgrade</a>. The <strong>Tiller</strong> component is now obsolete.</p>
<p>There is no command <code>helm init</code> therefore also the flag <code>--service-account</code> is removed.</p>
<blockquote>
<p>The internal implementation of Helm 3 has changed considerably from Helm 2. The most apparent change is the <strong>removal of Tiller</strong>.</p>
</blockquote>
