Helm Pull

helm pull

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 can also be used to perform cryptographic verification of a chart without installing the chart.

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

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

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

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 untardir are specified, untardir 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 pull
  6. --insecure-skip-tls-verify skip tls certificate checks for the chart download
  7. --key-file string identify HTTPS client using this SSL key file
  8. --keyring string location of public keys used for verification (default "~/.gnupg/pubring.gpg")
  9. --pass-credentials pass credentials to all domains
  10. --password string chart repository password where to locate the requested chart
  11. --plain-http use insecure HTTP connections for the chart download
  12. --prov fetch the provenance file, but don't perform verification
  13. --repo string chart repository url where to locate the requested chart
  14. --untar if set to true, will untar the chart after downloading it
  15. --untardir string if untar is specified, this flag specifies the name of the directory into which the chart is expanded (default ".")
  16. --username string chart repository username where to locate the requested chart
  17. --verify verify the package before using it
  18. --version string specify a version constraint for the chart version to use. This constraint can be a specific tag (e.g. 1.1.1) or it may reference a valid range (e.g. ^2.0.0). If this is not specified, the latest version is used

Options inherited from parent commands

  1. --burst-limit int client-side default throttling limit (default 100)
  2. --debug enable verbose output
  3. --kube-apiserver string the address and the port for the Kubernetes API server
  4. --kube-as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups.
  5. --kube-as-user string username to impersonate for the operation
  6. --kube-ca-file string the certificate authority file for the Kubernetes API server connection
  7. --kube-context string name of the kubeconfig context to use
  8. --kube-insecure-skip-tls-verify if true, the Kubernetes API server's certificate will not be checked for validity. This will make your HTTPS connections insecure
  9. --kube-tls-server-name string server name to use for Kubernetes API server certificate validation. If it is not provided, the hostname used to contact the server is used
  10. --kube-token string bearer token used for authentication
  11. --kubeconfig string path to the kubeconfig file
  12. -n, --namespace string namespace scope for this request
  13. --registry-config string path to the registry config file (default "~/.config/helm/registry/config.json")
  14. --repository-cache string path to the file containing cached repository indexes (default "~/.cache/helm/repository")
  15. --repository-config string path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")

SEE ALSO

  • helm - The Helm package manager for Kubernetes.
Auto generated by spf13/cobra on 27-Sep-2023