This document captures information about using Helm in specific Kubernetes environments.
We are trying to add more details to this document. Please contribute via Pull Requests if you can.
Helm is tested and known to work with minikube. It requires no additional configuration.
Hyperkube configured via scripts/local-cluster.sh
is known to work. For raw
Hyperkube you may need to do some manual configuration.
Google's GKE hosted Kubernetes platform is known to work with Helm, and requires no additional configuration.
Kubernetes bootstrapped with kubeadm
is known to work on the following Linux
distributions:
- Ubuntu 16.04
- CAN SOMEONE CONFIRM ON FEDORA?
Some versions of Helm (v2.0.0-beta2) require you to export KUBECONFIG=/etc/kubernetes/admin.conf
or create a ~/.kube/config
.
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 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 docs.