upstream/helm
1
0
Fork 0
mirror of https://github.com/helm/helm.git synced 2026-04-23 15:17:05 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
helm/docs/helm/helm_init.md
Matt Butcher 0853f4906a
feat(tiller): limit number of versions stored per release 
This adds a new configuration option to Tiller to limit the number of
records stored per release.

Tiller stores historical release information (helm history, helm
rollback). This makes it possible to set a maximum number of versions
per release.

To enable this feature, use `helm init --history-max NNN`. Note that
because of the restrictions on Deployment objects, you will have to
re-install Tiller to add a limit.

Along the way, I found an unreported bug in the Memory storage driver.
This fixes that bug and adds substantially more tests to catch
regressions.

Closes #2332
2017-08-10 12:01:20 -06:00

2.8 KiB
Raw Blame History

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.

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
      --history-max int          limit the maximum number of revisions saved per release. Use 0 for no limit.
      --local-repo-url string    URL for local repository (default "http://127.0.0.1:8879/charts")
      --net-host                 install Tiller with net=host
      --service-account string   name of service account
      --skip-refresh             do not refresh (download) the local repository cache
      --stable-repo-url string   URL for stable repository (default "https://kubernetes-charts.storage.googleapis.com")
  -i, --tiller-image string      override Tiller image
      --tiller-tls               install Tiller with TLS enabled
      --tiller-tls-cert string   path to TLS certificate file to install with Tiller
      --tiller-tls-key string    path to TLS key file to install with Tiller
      --tiller-tls-verify        install Tiller with TLS enabled and to verify remote certificates
      --tls-ca-cert string       path to CA root certificate
      --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 "$HOME/.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.
Auto generated by spf13/cobra on 10-Aug-2017