github.com/felipejfc/helm@v2.1.2+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/kubernetes/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  A: We no longer use GitHub releases. Binaries are now stored in a
    17  [GCS public bucket](https://kubernetes-helm.storage.googleapis.com).
    18  
    19  **Q: Why aren't there Debian/Fedora/... native packages of Helm?**
    20  
    21  We'd love to provide these or point you toward a trusted provider. If you're
    22  interested in helping, we'd love it. This is how the Homebrew formula was
    23  started.
    24  
    25  **Q: Why do you provide a `curl ...|bash` script?**
    26  
    27  A: There is a script in our repository (`scripts/get`) that can be executed as
    28  a `curl ..|bash` script. The transfers are all protected by HTTPS, and the script
    29  does some auditing of the packages it fetches. However, the script has all the
    30  usual dangers of any shell script.
    31  
    32  We provide it because it is useful, but we suggest that users carefully read the
    33  script first. What we'd really like, though, are better packaged releases of
    34  Helm.
    35  
    36  ## Installing
    37  
    38  I'm trying to install Helm/Tiller, but something is not right.
    39  
    40  **Q: How do I put the Helm client files somewhere other than ~/.helm?**
    41  
    42  Set the `$HELM_HOME` environment variable, and then run `helm init`:
    43  
    44  ```console
    45  export HELM_HOME=/some/path
    46  helm init --client-only
    47  ```
    48  
    49  Note that if you have existing repositories, you will need to re-add them
    50  with `helm repo add...`.
    51  
    52  **Q: How do I configure Helm, but not install Tiller?**
    53  
    54  By default, `helm init` will ensure that the local `$HELM_HOME` is configured,
    55  and then install Tiller on your cluster. To locally configure, but not install
    56  Tiller, use `helm init --client-only`.
    57  
    58  **Q: How do I manually install Tiller on the cluster?**
    59  
    60  Tiller is installed as a Kubernetes `deployment`. You can get the manifest
    61  by running `helm init --dry-run --debug`, and then manually install it with
    62  `kubectl`. It is suggested that you do not remove or change the labels on that
    63  deployment, as they are sometimes used by supporting scripts and tools.
    64  
    65  
    66  ## Getting Started
    67  
    68  I successfully installed Helm/Tiller but I can't use it.
    69  
    70  **Q: Trying to use Helm, I get the error "client transport was broken"**
    71  
    72  ```
    73  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.
    74  2016/10/14 02:26:32 transport: http2Client.notifyError got notified that the client transport was broken EOF.
    75  Error: transport is closing
    76  ```
    77  
    78  A: This is usually a good indication that Kubernetes is not set up to allow port forwarding.
    79  
    80  Typically, the missing piece is `socat`. If you are running CoreOS, we have been
    81  told that it may have been misconfigured on installation. The CoreOS team
    82  recommends reading this:
    83  
    84  - https://coreos.com/kubernetes/docs/latest/kubelet-wrapper.html
    85  
    86  Here are a few resolved issues that may help you get started:
    87  
    88  - https://github.com/kubernetes/helm/issues/1371
    89  - https://github.com/kubernetes/helm/issues/966
    90  
    91  **Q: Trying to use Helm, I get the error "lookup XXXXX on 8.8.8.8:53: no such host"**
    92  
    93  ```
    94  Error: Error forwarding ports: error upgrading connection: dial tcp: lookup kube-4gb-lon1-02 on 8.8.8.8:53: no such host
    95  ```
    96  
    97  A: We have seen this issue with Ubuntu and Kubeadm in multi-node clusters. The
    98  issue is that the nodes expect certain DNS records to be obtainable via global
    99  DNS. Until this is resolved upstream, you can work around the issue as
   100  follows:
   101  
   102  1) Add entries to `/etc/hosts` on the master mapping your hostnames to their public IPs
   103  2) Install `dnsmasq` on the master (e.g. `apt install -y dnsmasq`)
   104  3) Kill the k8s api server container on master (kubelet will recreate it)
   105  4) Then `systemctl restart docker` (or reboot the master) for it to pick up the /etc/resolv.conf changes
   106  
   107  See this issue for more information: https://github.com/kubernetes/helm/issues/1455
   108  
   109  ## Upgrading
   110  
   111  My Helm used to work, then I upgrade. Now it is broken.
   112  
   113  **Q: After upgrade, I get the error "Client version is incompatible". What's wrong?**
   114  
   115  Tiller and Helm have to negotiate a common version to make sure that they can safely
   116  communicate without breaking API assumptions. That error means that the version
   117  difference is too great to safely continue. Typically, you need to upgrade
   118  Tiller manually for this.
   119  
   120  The [Installation Guide](install.yaml) has definitive information about safely
   121  upgrading Helm and Tiller.
   122  
   123  The rules for version numbers are as follows:
   124  
   125  - Pre-release versions are incompatible with everything else. `Alpha.1` is incompatible with `Alpha.2`.
   126  - Patch revisions _are compatible_: 1.2.3 is compatible with 1.2.4
   127  - Minor revisions _are not compatible_: 1.2.0 is not compatible with 1.3.0,
   128    though we may relax this constraint in the future.
   129  - Major revisions _are not compatible_: 1.0.0 is not compatible with 2.0.0.
   130  
   131  ## Uninstalling
   132  
   133  I am trying to remove stuff.
   134  
   135  **Q: When I delete the Tiller deployment, how come all the releases are still there?**
   136  
   137  Releases are stored in ConfigMaps inside of the `kube-system` namespace. You will
   138  have to manually delete them to get rid of the record.
   139  
   140  **Q: I want to delete my local Helm. Where are all its files?**
   141  
   142  Along with the `helm` binary, Helm stores some files in `$HELM_HOME`, which is
   143  located by default in `~/.helm`.