github.com/koderover/helm@v2.17.0+incompatible/docs/install_faq.md (about) 1 # Installation: Frequently Asked Questions 2 3 This section tracks some of the more frequently encountered issues with installing 4 or getting started with Helm. 5 6 **We'd love your help** making this document better. To add, correct, or remove 7 information, [file an issue](https://github.com/helm/helm/issues) or 8 send us a pull request. 9 10 ## Downloading 11 12 I want to know more about my downloading options. 13 14 **Q: I can't get to GitHub releases of the newest Helm. Where are they?** 15 16 Binaries are stored at [get.helm.sh](https://get.helm.sh). 17 18 **Q: Why aren't there native packages of Helm for Fedora and other Linux distros?** 19 20 We'd love to provide these or point you toward a trusted provider. If you're 21 interested in helping, we'd love it. This is how the Homebrew formula was 22 started. 23 24 **Q: Why do you provide a `curl ...|bash` script?** 25 26 A: There is a script in our repository (`scripts/get`) that can be executed as 27 a `curl ..|bash` script. The transfers are all protected by HTTPS, and the script 28 does some auditing of the packages it fetches. However, the script has all the 29 usual dangers of any shell script. 30 31 We provide it because it is useful, but we suggest that users carefully read the 32 script first. What we'd really like, though, are better packaged releases of 33 Helm. 34 35 ## Installing 36 37 I'm trying to install Helm/Tiller, but something is not right. 38 39 **Q: How do I put the Helm client files somewhere other than ~/.helm?** 40 41 Set the `$HELM_HOME` environment variable, and then run `helm init`: 42 43 ```console 44 export HELM_HOME=/some/path 45 helm init --client-only 46 ``` 47 48 Note that if you have existing repositories, you will need to re-add them 49 with `helm repo add...`. 50 51 **Q: How do I configure Helm, but not install Tiller?** 52 53 A: By default, `helm init` will ensure that the local `$HELM_HOME` is configured, 54 and then install Tiller on your cluster. To locally configure, but not install 55 Tiller, use `helm init --client-only`. 56 57 **Q: How do I manually install Tiller on the cluster?** 58 59 A: Tiller is installed as a Kubernetes `deployment`. You can get the manifest 60 by running `helm init --dry-run --debug`, and then manually install it with 61 `kubectl`. It is suggested that you do not remove or change the labels on that 62 deployment, as they are sometimes used by supporting scripts and tools. 63 64 **Q: Why do I get `Error response from daemon: target is unknown` during Tiller install?** 65 66 A: Users have reported being unable to install Tiller on Kubernetes instances that 67 are using Docker 1.13.0. The root cause of this was a bug in Docker that made 68 that one version incompatible with images pushed to the Docker registry by 69 earlier versions of Docker. 70 71 This [issue](https://github.com/docker/docker/issues/30083) was fixed shortly 72 after the release, and is available in Docker 1.13.1-RC1 and later. 73 74 ## Getting Started 75 76 I successfully installed Helm/Tiller but I can't use it. 77 78 **Q: Trying to use Helm, I get the error "client transport was broken"** 79 80 ``` 81 E1014 02:26:32.885226 16143 portforward.go:329] an error occurred forwarding 37008 -> 44134: error forwarding port 44134 to pod tiller-deploy-2117266891-e4lev_kube-system, uid : unable to do port forwarding: socat not found. 82 2016/10/14 02:26:32 transport: http2Client.notifyError got notified that the client transport was broken EOF. 83 Error: transport is closing 84 ``` 85 86 A: This is usually a good indication that Kubernetes is not set up to allow port forwarding. 87 88 Typically, the missing piece is `socat`. If you are running CoreOS, we have been 89 told that it may have been misconfigured on installation. The CoreOS team 90 recommends reading this: 91 92 - https://coreos.com/kubernetes/docs/latest/kubelet-wrapper.html 93 94 Here are a few resolved issues that may help you get started: 95 96 - https://github.com/helm/helm/issues/1371 97 - https://github.com/helm/helm/issues/966 98 99 **Q: Trying to use Helm, I get the error "lookup XXXXX on 8.8.8.8:53: no such host"** 100 101 ``` 102 Error: Error forwarding ports: error upgrading connection: dial tcp: lookup kube-4gb-lon1-02 on 8.8.8.8:53: no such host 103 ``` 104 105 A: We have seen this issue with Ubuntu and Kubeadm in multi-node clusters. The 106 issue is that the nodes expect certain DNS records to be obtainable via global 107 DNS. Until this is resolved upstream, you can work around the issue as 108 follows. On each of the control plane nodes: 109 110 1) Add entries to `/etc/hosts`, mapping your hostnames to their public IPs 111 2) Install `dnsmasq` (e.g. `apt install -y dnsmasq`) 112 3) Remove the k8s api server container (kubelet will recreate it) 113 4) Then `systemctl restart docker` (or reboot the node) for it to pick up the /etc/resolv.conf changes 114 115 See this issue for more information: https://github.com/helm/helm/issues/1455 116 117 **Q: On GKE (Google Container Engine) I get "No SSH tunnels currently open"** 118 119 ``` 120 Error: Error forwarding ports: error upgrading connection: No SSH tunnels currently open. Were the targets able to accept an ssh-key for user "gke-[redacted]"? 121 ``` 122 123 Another variation of the error message is: 124 125 126 ``` 127 Unable to connect to the server: x509: certificate signed by unknown authority 128 129 ``` 130 131 A: The issue is that your local Kubernetes config file must have the correct credentials. 132 133 When you create a cluster on GKE, it will give you credentials, including SSL 134 certificates and certificate authorities. These need to be stored in a Kubernetes 135 config file (Default: `~/.kube/config` so that `kubectl` and `helm` can access 136 them. 137 138 **Q: When I run a Helm command, I get an error about the tunnel or proxy** 139 140 A: Helm uses the Kubernetes proxy service to connect to the Tiller server. 141 If the command `kubectl proxy` does not work for you, neither will Helm. 142 Typically, the error is related to a missing `socat` service. 143 144 **Q: Tiller crashes with a panic** 145 146 When I run a command on Helm, Tiller crashes with an error like this: 147 148 ``` 149 Tiller is listening on :44134 150 Probes server is listening on :44135 151 Storage driver is ConfigMap 152 Cannot initialize Kubernetes connection: the server has asked for the client to provide credentials 2016-12-20 15:18:40.545739 I | storage.go:37: Getting release "bailing-chinchilla" (v1) from storage 153 panic: runtime error: invalid memory address or nil pointer dereference 154 [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8053d5] 155 156 goroutine 77 [running]: 157 panic(0x1abbfc0, 0xc42000a040) 158 /usr/local/go/src/runtime/panic.go:500 +0x1a1 159 k8s.io/helm/vendor/k8s.io/kubernetes/pkg/client/unversioned.(*ConfigMaps).Get(0xc4200c6200, 0xc420536100, 0x15, 0x1ca7431, 0x6, 0xc42016b6a0) 160 /home/ubuntu/.go_workspace/src/k8s.io/helm/vendor/k8s.io/kubernetes/pkg/client/unversioned/configmap.go:58 +0x75 161 k8s.io/helm/pkg/storage/driver.(*ConfigMaps).Get(0xc4201d6190, 0xc420536100, 0x15, 0xc420536100, 0x15, 0xc4205360c0) 162 /home/ubuntu/.go_workspace/src/k8s.io/helm/pkg/storage/driver/cfgmaps.go:69 +0x62 163 k8s.io/helm/pkg/storage.(*Storage).Get(0xc4201d61a0, 0xc4205360c0, 0x12, 0xc400000001, 0x12, 0x0, 0xc420200070) 164 /home/ubuntu/.go_workspace/src/k8s.io/helm/pkg/storage/storage.go:38 +0x160 165 k8s.io/helm/pkg/tiller.(*ReleaseServer).uniqName(0xc42002a000, 0x0, 0x0, 0xc42016b800, 0xd66a13, 0xc42055a040, 0xc420558050, 0xc420122001) 166 /home/ubuntu/.go_workspace/src/k8s.io/helm/pkg/tiller/release_server.go:577 +0xd7 167 k8s.io/helm/pkg/tiller.(*ReleaseServer).prepareRelease(0xc42002a000, 0xc42027c1e0, 0xc42002a001, 0xc42016bad0, 0xc42016ba08) 168 /home/ubuntu/.go_workspace/src/k8s.io/helm/pkg/tiller/release_server.go:630 +0x71 169 k8s.io/helm/pkg/tiller.(*ReleaseServer).InstallRelease(0xc42002a000, 0x7f284c434068, 0xc420250c00, 0xc42027c1e0, 0x0, 0x31a9, 0x31a9) 170 /home/ubuntu/.go_workspace/src/k8s.io/helm/pkg/tiller/release_server.go:604 +0x78 171 k8s.io/helm/pkg/proto/hapi/services._ReleaseService_InstallRelease_Handler(0x1c51f80, 0xc42002a000, 0x7f284c434068, 0xc420250c00, 0xc42027c190, 0x0, 0x0, 0x0, 0x0, 0x0) 172 /home/ubuntu/.go_workspace/src/k8s.io/helm/pkg/proto/hapi/services/tiller.pb.go:747 +0x27d 173 k8s.io/helm/vendor/google.golang.org/grpc.(*Server).processUnaryRPC(0xc4202f3ea0, 0x28610a0, 0xc420078000, 0xc420264690, 0xc420166150, 0x288cbe8, 0xc420250bd0, 0x0, 0x0) 174 /home/ubuntu/.go_workspace/src/k8s.io/helm/vendor/google.golang.org/grpc/server.go:608 +0xc50 175 k8s.io/helm/vendor/google.golang.org/grpc.(*Server).handleStream(0xc4202f3ea0, 0x28610a0, 0xc420078000, 0xc420264690, 0xc420250bd0) 176 /home/ubuntu/.go_workspace/src/k8s.io/helm/vendor/google.golang.org/grpc/server.go:766 +0x6b0 177 k8s.io/helm/vendor/google.golang.org/grpc.(*Server).serveStreams.func1.1(0xc420124710, 0xc4202f3ea0, 0x28610a0, 0xc420078000, 0xc420264690) 178 /home/ubuntu/.go_workspace/src/k8s.io/helm/vendor/google.golang.org/grpc/server.go:419 +0xab 179 created by k8s.io/helm/vendor/google.golang.org/grpc.(*Server).serveStreams.func1 180 /home/ubuntu/.go_workspace/src/k8s.io/helm/vendor/google.golang.org/grpc/server.go:420 +0xa3 181 ``` 182 183 A: Check your security settings for Kubernetes. 184 185 A panic in Tiller is almost always the result of a failure to negotiate with the 186 Kubernetes API server (at which point Tiller can no longer do anything useful, so 187 it panics and exits). 188 189 Often, this is a result of authentication failing because the Pod in which Tiller 190 is running does not have the right token. 191 192 To fix this, you will need to change your Kubernetes configuration. Make sure 193 that `--service-account-private-key-file` from `controller-manager` and 194 `--service-account-key-file` from apiserver point to the _same_ x509 RSA key. 195 196 197 ## Upgrading 198 199 My Helm used to work, then I upgrade. Now it is broken. 200 201 **Q: After upgrade, I get the error "Client version is incompatible". What's wrong?** 202 203 Tiller and Helm have to negotiate a common version to make sure that they can safely 204 communicate without breaking API assumptions. That error means that the version 205 difference is too great to safely continue. Typically, you need to upgrade 206 Tiller manually for this. 207 208 The [Installation Guide](install.md) has definitive information about safely 209 upgrading Helm and Tiller. 210 211 The rules for version numbers are as follows: 212 213 - Pre-release versions are incompatible with everything else. `Alpha.1` is incompatible with `Alpha.2`. 214 - Patch revisions _are compatible_: 1.2.3 is compatible with 1.2.4 215 - Minor revisions _are not compatible_: 1.2.0 is not compatible with 1.3.0, 216 though we may relax this constraint in the future. 217 - Major revisions _are not compatible_: 1.0.0 is not compatible with 2.0.0. 218 219 ## Uninstalling 220 221 I am trying to remove stuff. 222 223 **Q: When I delete the Tiller deployment, how come all the releases are still there?** 224 225 Releases are stored in ConfigMaps inside of the `kube-system` namespace. You will 226 have to manually delete them to get rid of the record, or use ```helm delete --purge```. 227 228 **Q: I want to delete my local Helm. Where are all its files?** 229 230 Along with the `helm` binary, Helm stores some files in `$HELM_HOME`, which is 231 located by default in `~/.helm`.