Difference between revisions of "Helm v2: helm init"

From wikieduonline
Jump to navigation Jump to search
Line 33: Line 33:
 
== Related ==
 
== Related ==
 
* <code>[[$HOME/.helm]]</code>
 
* <code>[[$HOME/.helm]]</code>
 +
* <code>[[helm init --upgrade]]</code>
  
 
== See also ==
 
== See also ==

Revision as of 06:38, 30 June 2022

helm init --stable-repo-url=https://charts.helm.sh/stable --service-account tiller --tiller-image ghcr.io/helm/tiller:v2.16.1
Creating /Users/YOUR_USER/.helm
Creating /Users/YOUR_USER/.helm/repository
Creating /Users/YOUR_USER/.helm/repository/cache
Creating /Users/YOUR_USER/.helm/repository/local
Creating /Users/YOUR_USER/.helm/plugins
Creating /Users/YOUR_USER/.helm/starters
Creating /Users/YOUR_USER/.helm/cache/archive
Creating /Users/YOUR_USER/.helm/repository/repositories.yaml
Adding stable repo with URL: https://charts.helm.sh/stable
Adding local repo with URL: http://127.0.0.1:8879/charts
$HELM_HOME has been configured at /Users/YOUR_USER/.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://v2.helm.sh/docs/securing_installation/


You can explicitly tell helm init to…

  • Install the canary build with the --canary-image flag
  • Install a particular image (version) with --tiller-image
  • Install to a particular cluster with --kube-context
  • Install into a particular namespace with --tiller-namespace
  • Install Tiller with a Service Account with --service-account (for RBAC enabled clusters)
  • Install Tiller without mounting a service account with --automount-service-account false

Related

See also

Advertising: