Helm Installation: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 11: Line 11:


  brew install kubernetes-helm
  brew install kubernetes-helm
==Upgrade==
brew upgrade kubernetes-helm


=Initialization=
=Initialization=

Revision as of 19:28, 21 October 2019

External

Internal

Installation on Mac

brew install kubernetes-helm

Upgrade

brew upgrade kubernetes-helm

Initialization

Then initialize Helm and install Tiller on the Kubernetes cluster from the current context (kubectl config current-context):

helm init --history-max 200
Creating /Users/ovidiufeodorov/.helm
Creating /Users/ovidiufeodorov/.helm/repository
Creating /Users/ovidiufeodorov/.helm/repository/cache
Creating /Users/ovidiufeodorov/.helm/repository/local
Creating /Users/ovidiufeodorov/.helm/plugins
Creating /Users/ovidiufeodorov/.helm/starters
Creating /Users/ovidiufeodorov/.helm/cache/archive
Creating /Users/ovidiufeodorov/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://127.0.0.1:8879/charts
$HELM_HOME has been configured at /Users/ovidiufeodorov/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation

Tiller components are installed in the "kube-system" namespace.

Advanced Initialization

https://helm.sh/docs/using_helm/#advanced-usage

How to Verify Whether Helm Was Initialized

Current solution: verify the presence of the ~/.helm directory.