-
Notifications
You must be signed in to change notification settings - Fork 12
Helm
Helm is a package manager for Kubernetes A helm chart is a peice of software run in a K8s cluter
from https://www.katacoda.com/courses/kubernetes/helm-package-manager
Install helm
curl -LO https://storage.googleapis.com/kubernetes-helm/helm-v2.8.2-linux-amd64.tar.gz
tar -xvf helm-v2.8.2-linux-amd64.tar.gz
mv linux-amd64/helm /usr/local/bin/
Initialize Helm on the server and client
helm init
Update helm charts so that they are up to date
helm repo update
Search for available helm charts
helm search <name_of_software>
example: helm search redis
Inspect a chart
helm inspect <name_of_chart_and_release>
example: helm inspect stable/redis
Deploy a chart to your cluster
helm deploy <name_of_chart_and_release>
example: helm deploy stable/redis
Look at what you've deployed with helm
helm ls
-
There are 2 parts to helm: the client and server. The server is tiller
-
If your client and server versions are out of sync, you will get an error when you run
helm init
- The error: when you run a helm command, you will see 'tiller not present in cluster. Have you run
helm init
?' - When you run
helm init
, you will see:warning: Tiller is already installed in this cluster
- The error: when you run a helm command, you will see 'tiller not present in cluster. Have you run
-
SOLUTION:
helm init --upgrade
-
A common error:
Error: UPGRADE FAILED: "contact-context-develop" has no deployed releases
-
It's a bug in helm. The fix:
helm delete --purge <releasename>
Use homebrew to switch versions of kubernetes-helm See here: https://github.com/helm/helm/issues/1523#issuecomment-423357734
$ brew install https://raw.githubusercontent.com/Homebrew/homebrew-core/78d64252f30a12b6f4b3ce29686ab5e262eea812/Formula/kubernetes-helm.rb
$ brew switch kubernetes-helm 2.9.1```