helm

The Helm package manager for Kubernetes.

Synopsis

The Kubernetes package manager

To begin working with Helm, run the ‘helm init’ command:

  1. $ helm init

This will install Tiller to your running Kubernetes cluster.It will also set up any necessary local configuration.

Common actions from this point include:

  • helm search: Search for charts
  • helm fetch: Download a chart to your local directory to view
  • helm install: Upload the chart to Kubernetes
  • helm list: List releases of charts

Environment:

  • $HELM-HOME: Set an alternative location for Helm files. By default, these are stored in ~/.helm
  • $HELM-HOST: Set an alternative Tiller host. The format is host:port
  • $HELM-NO-PLUGINS: Disable plugins. Set HELM-NO-PLUGINS=1 to disable plugins.
  • $TILLER-NAMESPACE: Set an alternative Tiller namespace (default “kube-system”)
  • $KUBECONFIG: Set an alternative Kubernetes configuration file (default “~/.kube/config”)
  • $HELM-TLS-CA-CERT: Path to TLS CA certificate used to verify the Helm client and Tiller server certificates (default “$HELM-HOME/ca.pem”)
  • $HELM-TLS-CERT: Path to TLS client certificate file for authenticating to Tiller (default “$HELM-HOME/cert.pem”)
  • $HELM-TLS-KEY: Path to TLS client key file for authenticating to Tiller (default “$HELM-HOME/key.pem”)
  • $HELM-TLS-ENABLE: Enable TLS connection between Helm and Tiller (default “false”)
  • $HELM-TLS-VERIFY: Enable TLS connection between Helm and Tiller and verify Tiller server certificate (default “false”)
  • $HELM-TLS-HOSTNAME: The hostname or IP address used to verify the Tiller server certificate (default “127.0.0.1”)
  • $HELM-KEY-PASSPHRASE: Set HELM-KEY-PASSPHRASE to the passphrase of your PGP private key. If set, you will not be prompted for the passphrase while signing helm charts

Options

  1. --debug Enable verbose output
  2. -h, --help help for helm
  3. --home string Location of your Helm config. Overrides $HELM-HOME (default "~/.helm")
  4. --host string Address of Tiller. Overrides $HELM-HOST
  5. --kube-context string Name of the kubeconfig context to use
  6. --kubeconfig string Absolute path of the kubeconfig file to be used
  7. --tiller-connection-timeout int The duration (in seconds) Helm will wait to establish a connection to Tiller (default 300)
  8. --tiller-namespace string Namespace of Tiller (default "kube-system")

SEE ALSO

Auto generated by spf13/cobra on 16-May-2019