Kubernetes Distribution Guide
This document captures information about using Helm in specific Kubernetes environments. Distros are sorted alphabetically so as to not imply any sort of preference.
We are trying to add more details to this document. Please contribute via Pull Requests if you can.
Helm works with Azure Kubernetes Service.
Helm has been tested and is working on Mesospheres DC/OS 1.11 Kubernetes platform, and requires no additional configuration.
Google’s GKE hosted Kubernetes platform is known to work with Helm, and 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.
Helm works with IBM Cloud Kubernetes Service.
KIND (Kubernetes IN Docker)
Helm is regularly tested on KIND.
Helm works in clusters that are set up by KubeOne without caveats.
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 their configuration.
Helm can be enabled in
MicroK8s using the command:
Helm is tested and known to work with Minikube. It requires no additional configuration.
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 is 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.
Kubernetes bootstrapped with
kubeadm is known to work on the following Linux
- Ubuntu 16.04
- Fedora release 25
Some versions of Helm (v2.0.0-beta2) require you to
export KUBECONFIG=/etc/kubernetes/admin.conf or create a