Ask questionsHelm3: No 'init', doesn't use existing ~/.helm

./helm version version.BuildInfo{Version:"v3.0.0-beta.1", GitCommit:"f76b5f21adb53a85de8925f4a9d4f9bd99f185b5", GitTreeState:"clean", GoVersion:"go1.12.9"}

I've upgraded from helm v2 by downloading the beta v3 client. I've deleted the tiller account with the v2 client. No helm commands using v3 seem to work -- it knows nothing about repositories. If I supply them on command line, it still doesn't DTRT:

➜  helm-darwin-amd64 ./helm --repository-cache ~/.helm/repository/cache --repository-config ~/.helm/repository/repositories.yaml repo update
Error: couldn't load repositories file (): open : no such file or directory

But it clearly can read the config therein:

➜  helm-darwin-amd64 ./helm --repository-cache ~/.helm/repository/cache --repository-config ~/.helm/repository/repositories.yaml repo list

But installing any chart fails:

➜  helm-darwin-amd64 ./helm --repository-cache ~/.helm/repository/cache --repository-config ~/.helm/repository/repositories.yaml install stable/kong --set ingressController.enabled=true -g
Error: failed to download "stable/kong" (hint: running `helm repo update` may help)
[1]    66253 exit 1     ./helm --repository-cache ~/.helm/repository/cache --repository-config

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? This is really not obvious. The docs on the all refer to v2 and talk about helm init and so on. If the docs are this unready then it's not in Beta, surely? This is just silly.

Can you please point out the docs that explain how to upgrade to v3 without losing all functionality? Surely they exist?


Answer questions joelbernstein

@hickeyma that worked! Thanks

➜  helm-darwin-amd64 ./helm repo update
Error: no repositories found. You must add one before updating
[1]    66403 exit 1     ./helm repo update
➜  helm-darwin-amd64 ./helm --repository-cache ~/.helm/repository/cache --repository-config ~/.helm/repository/repositories.yaml repo update
Hang tight while we grab the latest from your chart repositories...
...Unable to get an update from the "local" chart repository (
	Get dial tcp connect: connection refused
...Successfully got an update from the "gitlab" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈```

Related questions

Error: validation: chart.metadata is required when using --repo - helm hot 4
"Error: Transport is closing" message when attempting to install hot 2
Error: open .helm\repository\cache\local-index.yaml hot 2
"helm dep build" fails if requirements.yaml contains local dependencies and remote one hot 2
Helm upgrade fails the release after adding a new resource hot 2
Error: could not find a ready tiller pod hot 2
Error: apiVersion 'v2' is not valid. The value must be "v1" hot 2
Unable to start Tiller pod, bind address already in use hot 2
Upgrading releases with immutable resources (e.g. persitentVolume) hot 2
helm 3: Not able to push chart to docker hub hot 1
`helm upgrade --recreate-pods` flag should do a soft restart - helm hot 1
No kind Job is registered for version batch/v1 hot 1
`Error: rendered manifests contain a resource that already exists` but nothing shows up on `helm list --all` - helm hot 1
error calling eq: invalid type for comparison hot 1
upgrade apiVersion in k8s from 1.14 to 1.16 FAILED hot 1
Github User Rank List