github.com/zoumo/helm@v2.5.0+incompatible/docs/kubernetes_distros.md (about)

     1  # Kubernetes Distribution Guide
     2  
     3  This document captures information about using Helm in specific Kubernetes
     4  environments.
     5  
     6  We are trying to add more details to this document. Please contribute via Pull
     7  Requests if you can.
     8  
     9  ## MiniKube
    10  
    11  Helm is tested and known to work with [minikube](https://github.com/kubernetes/minikube).
    12  It requires no additional configuration.
    13  
    14  ## `scripts/local-cluster` and Hyperkube
    15  
    16  Hyperkube configured via `scripts/local-cluster.sh` is known to work. For raw
    17  Hyperkube you may need to do some manual configuration.
    18  
    19  ## GKE
    20  
    21  Google's GKE hosted Kubernetes platform is known to work with Helm, and requires
    22  no additional configuration.
    23  
    24  ## Ubuntu with 'kubeadm'
    25  
    26  Kubernetes bootstrapped with `kubeadm` is known to work on the following Linux
    27  distributions:
    28  
    29  - Ubuntu 16.04
    30  - CAN SOMEONE CONFIRM ON FEDORA?
    31  
    32  Some versions of Helm (v2.0.0-beta2) require you to `export KUBECONFIG=/etc/kubernetes/admin.conf`
    33  or create a `~/.kube/config`.
    34  
    35  ## Container Linux by CoreOS
    36  
    37  Helm requires that kubelet have access to a copy of the `socat` program to proxy connections to the Tiller API. On Container Linux the Kubelet runs inside of a [hyperkube](https://github.com/kubernetes/kubernetes/tree/master/cluster/images/hyperkube) container image that has socat. So, even though Container Linux doesn't ship `socat` the container filesystem running kubelet does have socat. To learn more read the [Kubelet Wrapper](https://coreos.com/kubernetes/docs/latest/kubelet-wrapper.html) docs.