Helm Package

helm package

package a chart directory into a chart archive

Synopsis

This command packages a chart into a versioned chart archive file. If a path is given, this will look at that path for a chart (which must contain a Chart.yaml file) and then package that directory.

Versioned chart archives are used by Helm package repositories.

To sign a chart, use the ‘—sign’ flag. In most cases, you should also provide ‘—keyring path/to/secret/keys’ and ‘—key keyname’.

$ helm package —sign ./mychart —key mykey —keyring ~/.gnupg/secring.gpg

If ‘—keyring’ is not specified, Helm usually defaults to the public keyring unless your environment is otherwise configured.

  1. helm package [CHART_PATH] [...] [flags]

Options

  1. --app-version string set the appVersion on the chart to this version
  2. -u, --dependency-update update dependencies from "Chart.yaml" to dir "charts/" before packaging
  3. -d, --destination string location to write the chart. (default ".")
  4. -h, --help help for package
  5. --key string name of the key to use when signing. Used if --sign is true
  6. --keyring string location of a public keyring (default "~/.gnupg/pubring.gpg")
  7. --passphrase-file string location of a file which contains the passphrase for the signing key. Use "-" in order to read from stdin.
  8. --sign use a PGP private key to sign this package
  9. --version string set the version on the chart to this semver version

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