If the directory is not present it will be created. Walterm21 mentioned this issue Dec 16, 2019. Found this out as per solution in helm/helm#6996. Try to reboot the Helm too with the following command: helm init After that you will be able to use the Helm without problems.


As with the rest of the Helm commands, ‘helm init’ discovers Kubernetes clusters by reading $KUBECONFIG (default ‘~/.kube/config’) and using the default context. According to the official documentation, the helm init command has been removed without replacement: The helm init command has been removed. If the docs are this unready then it's not in Beta, surely? helm init works without issue, but helm list, helm install, and so on all do not work, citing some missing permission or another."

helm init not working with version 3. I tried with 2.14.2 and it did work.

Copy link Quote reply Member bacongobbler … When installing Tiller, ‘helm init’ will attempt to … This is really not obvious. use 2.14.2 : choco install kubernetes-helm --version=2.14.2 -y helm init --upgrade --service-account tiller Tiller is removed from helm v3.0 #20.
It performed two primary functions. share | improve this answer | follow | edited Jan 7 at 11:26. answered Oct 20 '19 at 2:19. valdeci valdeci. First, it installed Tiller. The command `helm init` doesn't exist in new versions of helm. The Quickstart Guide of version 3 beta still contains helm init step. I get that it has been removed by when I do a helm list I got no charts listed. I know it's a beta and initialization isn't the most important part. To set up just a local environment, use ‘–client-only’. This is no longer needed. Why not add a virtual subcommand helm init like in v2, which either reconfigures helm based on v2 config, or explains properly how to modify the existing config? And without init, helm cli isn't working correctly. 6,229 3 3 gold badges 34 34 silver badges 51 51 bronze badges. Last version with init command is version v3.0.0-alpha.2. 0.

The docs on the v3.helm.sh/docs all refer to v2 and talk about helm init and so on. Second, it setup directories and repositories where Helm configuration lived. This is now automated. "When installing a cluster for the first time using kubeadm v1.6.1, the initialization defaults to setting up RBAC controlled access, which messes with permissions needed by Tiller to do installations, scan for installed components, and so on. add a comment | 1.

That will configure $HELM_HOME, but not attempt to connect to a Kubernetes cluster and install the Tiller deployment. Closed Copy link Quote reply jgschmitz commented Jan 10, 2020.