Skip to main content
In this lesson we cover installing and configuring Helm so you can manage Kubernetes applications using charts. Before installing Helm, confirm you have a working Kubernetes cluster and a configured kubectl client. Helm uses your kubeconfig to talk to the cluster, so ensure it points to the intended cluster context.
A dark presentation slide titled "Install & Configuration" showing the Helm logo (a ship's wheel with the word HELM) in the center-right. The KodeKloud branding appears in the top-right corner.
Make sure kubectl can talk to your cluster and that your kubeconfig is accessible from your user home directory. Snap-installed Helm (see below) requires a less restrictive sandbox to read kubeconfig by default.
Prerequisites
  • A running Kubernetes cluster (local, cloud, or remote).
  • kubectl installed and configured with the correct kubeconfig.
  • Network access to download Helm binaries or packages.
Quick verification commands:
Install Helm (platforms and common methods) The examples below focus on common installation methods for Linux and also show macOS/Windows alternatives. Note: The --classic flag is required for Snap installs to relax confinement so Helm can read files from standard locations (like kubeconfig) on the host. Install examples (step-by-step)
  • Snap (Linux):
  • Debian / Ubuntu (APT):
  • FreeBSD:
  • macOS:
  • Windows (PowerShell with Chocolatey):
Verify Helm is installed and operational
Troubleshooting tips and important notes
If you installed Helm via Snap and Helm cannot access your kubeconfig, the Snap confinement may be blocking access. Use the --classic option on install or place kubeconfig in a location the snap can read. Always verify kubectl can reach the cluster before troubleshooting Helm connectivity issues.
  • Ensure kubectl works first: most Helm connectivity problems are kubeconfig/context related.
  • Helm 3 removed the server-side Tiller component; everything runs client-side communicating with the Kubernetes API.
  • Keep Helm updated via your chosen package manager to receive chart tooling and security fixes.
References and further reading Practice suggestion
  • In a lab environment, install Helm using one of the methods above, add a chart repository (for example Bitnami), and deploy a simple chart (e.g., nginx) to validate end-to-end functionality.

Watch Video

Practice Lab