Skip to main content
This lesson covers the prerequisites and common installation methods for Helm, plus quick verification steps to confirm Helm can talk to your Kubernetes cluster. Prerequisites
  • A running Kubernetes cluster (local or remote).
  • kubectl installed and configured on your workstation, with the correct cluster context selected in your kubeconfig so Helm targets the intended cluster.
Before installing Helm, confirm kubectl can reach your cluster. For example, kubectl get nodes should return the cluster nodes and not an error. If kubectl fails, fix your kubeconfig or cluster access before proceeding.
A dark presentation slide showing the Helm logo on the right and the text "Install & Configuration" on the left.
Supported platforms
  • Linux, macOS, and Windows are supported.
  • Choose an installer that matches your OS and distribution.
Common installation methods (Linux-focused) Below is a concise summary of common Linux installation options and when to use them. Example installation commands (Linux)
Other platforms Quick verification After installation, run the following to verify Helm is installed and can access the cluster:
  1. Check Helm client and server versions:
  1. Confirm Helm can list releases in the cluster:
  1. If you added a repo, update and list repos:
Troubleshooting tips
  • If helm commands fail with authentication or connectivity errors, confirm kubectl works first:
    • kubectl config current-context
    • kubectl get nodes
  • On systems using snap, omit --classic only if you intentionally want strict sandboxing and have arranged alternative kubeconfig access.
References and further reading Practice exercise Install Helm on your workstation using one of the methods above, then verify:
  • helm version returns the client and (if applicable) server version,
  • helm list --all-namespaces runs without cluster-access errors.
That completes this section — move on once Helm is installed and verified to communicate with your Kubernetes cluster.

Watch Video

Practice Lab