1.9 KiB
helm init
initialize Helm on both client and server
Synopsis
This command installs Tiller (the helm server side component) onto your Kubernetes Cluster and sets up local configuration in $HELM_HOME (default ~/.helm/)
As with the rest of the Helm commands, 'helm init' discovers Kubernetes clusters by reading $KUBECONFIG (default '~/.kube/config') and using the default context.
To set up just a local environment, use '--client-only'. That will configure $HELM_HOME, but not attempt to connect to a remote cluster and install the Tiller deployment.
When installing Tiller, 'helm init' will attempt to install the latest released version. You can specify an alternative image with '--tiller-image'. For those frequently working on the latest code, the flag '--canary-image' will install the latest pre-release version of Tiller (e.g. the HEAD commit in the GitHub repository on the master branch).
To dump a manifest containing the Tiller deployment YAML, combine the '--dry-run' and '--debug' flags.
helm init
Options
--canary-image use the canary tiller image
-c, --client-only if set does not install tiller
--dry-run do not install local or remote
-i, --tiller-image string override tiller image
--upgrade upgrade if tiller is already installed
Options inherited from parent commands
--debug enable verbose output
--home string location of your Helm config. Overrides $HELM_HOME (default "~/.helm")
--host string address of tiller. Overrides $HELM_HOST
--kube-context string name of the kubeconfig context to use
--tiller-namespace string namespace of tiller (default "kube-system")
SEE ALSO
- helm - The Helm package manager for Kubernetes.