Initializing_Helm_V2_

Initializing V2

Helm v3 does not need to be initialized.

As always, you can build Helm from source, or download a tarball. We expect to see Linux packages for the stable release soon. The current RBAC security requirements to deploy helm require the creation of a new serviceaccount and assigning of permissions and roles. There are several optional settings which can be passed to the helm init command, typically for particular security concerns, storage options and also a dry-run option.

helm init
...
Tiller (the helm server side component) has been installed into your Kubernetes Cluster.
Happy Helming!

$ kubectl get deployments --namespace=kube-system
NAMESPACE    NAME           READY  UP-TO-DATE  AVAILABLE  AGE
kube-system  tiller-deploy  1/1    1           1          15s

The helm v2 initialization should have created a new tiller-deploy pod in your cluster. Please note that this will create a deployment in the kube-system namespace.

The client will be able to communicate with the tiller pod using port forwarding. Hence, you will not see any service exposing tiller.