helm fetch

Download a chart from a repository and (optionally) unpack it in local directory

Synopsis

Retrieve a package from a package repository, and download it locally.

This is useful for fetching packages to inspect, modify, or repackage. It canalso be used to perform cryptographic verification of a chart without installingthe chart.

There are options for unpacking the chart after download. This will create adirectory for the chart and uncompress into that directory.

If the –verify flag is specified, the requested chart MUST have a provenancefile, and MUST pass the verification process. Failure in any part of this willresult in an error, and the chart will not be saved locally.

  1. helm fetch [flags] [chart URL | repo/chartname] [...]

Options

  1. --ca-file string Verify certificates of HTTPS-enabled servers using this CA bundle
  2. --cert-file string Identify HTTPS client using this SSL certificate file
  3. -d, --destination string Location to write the chart. If this and tardir are specified, tardir is appended to this (default ".")
  4. --devel Use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored.
  5. -h, --help help for fetch
  6. --key-file string Identify HTTPS client using this SSL key file
  7. --keyring string Keyring containing public keys (default "~/.gnupg/pubring.gpg")
  8. --password string Chart repository password
  9. --prov Fetch the provenance file, but don't perform verification
  10. --repo string Chart repository url where to locate the requested chart
  11. --untar If set to true, will untar the chart after downloading it
  12. --untardir string If untar is specified, this flag specifies the name of the directory into which the chart is expanded (default ".")
  13. --username string Chart repository username
  14. --verify Verify the package against its signature
  15. --version string Specific version of a chart. Without this, the latest version is fetched

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 16-May-2019