Menu
The command helm init does not work any longer as of version 3.
Running helm --help lists all available commands, amongst which init is no longer present.
Why is that?
872
The helm init command has been removed. It performed two primary functions. First, it installed Tiller. This is no longer needed.
Helm 2 used config-maps to store release information. In Helm 3, secrets are used instead as the default storage driver. Also, they are stored in the same namespace where the release is deployed. Previously, the release information was stored in the same namespace where tiller is deployed.
In helm 3 there is no tiller component. Helm client directly interacts with the kubernetes API for the helm chart deployment. So from wherever you are running the helm command, you should have kubectl configured with cluster-admin permissions for helm to execute the manifests in the chart.
9.0. The common platform binaries are here: MacOS amd64 (checksum / 7e5a2f2a6696acf278ea17401ade5c35430e2caa57f67d4aa99c607edcc08f5e)
According to the official documentation, the helm init command has been removed without replacement:
The helm init command has been removed. It performed two primary functions. First, it installed Tiller. This is no longer needed. Second, it setup directories and repositories where Helm configuration lived. This is now automated. If the directory is not present it will be created.
There has been another notable change, which might trouble you next:
The
stablerepository is no longer added by default. This repository will be deprecated during the life of Helm v3 and we are now moving to a distributed model of repositories that can be searched by the Helm Hub.
However, according to the official quickstart guide, this can be done manually if desired:
$ helm repo add stable https://charts.helm.sh/stable
$ helm repo update
⎈ Happy Helming!⎈
149
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With