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 Kubernetes 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.

  1. helm init [flags]

Options

  1.       --automount-service-account-token    Auto-mount the given service account to tiller (default true)
  2.       --canary-image                       Use the canary Tiller image
  3.   -c, --client-only                        If set does not install Tiller
  4.       --dry-run                            Do not install local or remote
  5.       --force-upgrade                      Force upgrade of Tiller to the current helm version
  6.   -h, --help                               help for init
  7.       --history-max int                    Limit the maximum number of revisions saved per release. Use 0 for no limit.
  8.       --local-repo-url string              URL for local repository (default "http://127.0.0.1:8879/charts")
  9.       --net-host                           Install Tiller with net=host
  10.       --node-selectors string              Labels to specify the node on which Tiller is installed (app=tiller,helm=rocks)
  11.   -o, --output OutputFormat                Skip installation and output Tiller's manifest in specified format (json or yaml)
  12.       --override stringArray               Override values for the Tiller Deployment manifest (can specify multiple or separate values with commas: key1=val1,key2=val2)
  13.       --replicas int                       Amount of tiller instances to run on the cluster (default 1)
  14.       --service-account string             Name of service account
  15.       --skip-refresh                       Do not refresh (download) the local repository cache
  16.       --skip-repos                         Skip adding the stable and local repositories
  17.       --stable-repo-url string             URL for stable repository (default "https://charts.helm.sh/stable")
  18.   -i, --tiller-image string                Override Tiller image
  19.       --tiller-tls                         Install Tiller with TLS enabled
  20.       --tiller-tls-cert string             Path to TLS certificate file to install with Tiller
  21.       --tiller-tls-hostname string         The server name used to verify the hostname on the returned certificates from Tiller
  22.       --tiller-tls-key string              Path to TLS key file to install with Tiller
  23.       --tiller-tls-verify                  Install Tiller with TLS enabled and to verify remote certificates
  24.       --tls-ca-cert string                 Path to CA root certificate
  25.       --upgrade                            Upgrade if Tiller is already installed
  26.       --use-deprecated-stable-repository   Use the old (googleapis) repository URL even though that URL is being shutdown.
  27.       --wait                               Block until Tiller is running and ready to receive requests

Options inherited from parent commands

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

SEE ALSO

  • helm - The Helm package manager for Kubernetes.
Auto generated by spf13/cobra on 15-Oct-2020