Kubernetes Distribution Guide
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 can be enabled in MicroK8s using the command:
Helm is tested and known to work with minikube. It requires no additional configuration.
scripts/local-cluster and Hyperkube
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 enables RBAC by default. You will need to create a service account for tiller, and use the –service-account flag when initializing the helm server.
See Tiller and role-based access control for more information.
Helm works with Azure Kubernetes Service. If using an RBAC-enabled AKS cluster, you need a service account and role binding for the Tiller service.
Helm works with IBM Cloud Kubernetes Service. IKS cluster enables RBAC by default and this means you will need a service account and role binding for the Tiller service.
Ubuntu with ‘kubeadm’
Kubernetes bootstrapped with
kubeadm is known to work on the following Linux
- Arch Linux
- Ubuntu 16.04
- Fedora release 25
Some versions of Helm (v2.0.0-beta2) require you to
or create a
Container Linux by CoreOS
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.
Helm works straightforward on OpenShift Online, OpenShift Dedicated, OpenShift Container Platform (version >= 3.6) or OpenShift Origin (version >= 3.6). To learn more read this blog post.
Helm Client and Helm Server (Tiller) are pre-installed with Platform9 Managed Kubernetes. Platform9 provides access to all official Helm charts through the App Catalog UI and native Kubernetes CLI. Additional repositories can be manually added. Further details are available in this Platform9 App Catalog article.
Helm (both client and server) has been tested and is working on Mesospheres DC/OS 1.11 Kubernetes platform, and requires no additional configuration.
Helm works in user clusters that are created by Kubermatic without caveats. Since seed cluster can be setup up in different ways Helm support depends on them.
Helm works in clusters that are set up by KubeOne without caveats.