Helm History

helm history

fetch release history

Synopsis

History prints historical revisions for a given release.

A default maximum of 256 revisions will be returned. Setting ‘—max’ configures the maximum length of the revision list returned.

The historical release set is printed as a formatted table, e.g:

  1. $ helm history angry-bird
  2. REVISION    UPDATED                     STATUS          CHART             APP VERSION     DESCRIPTION
  3. 1           Mon Oct 3 10:15:13 2016     superseded      alpine-0.1.0      1.0             Initial install
  4. 2           Mon Oct 3 10:15:13 2016     superseded      alpine-0.1.0      1.0             Upgraded successfully
  5. 3           Mon Oct 3 10:15:13 2016     superseded      alpine-0.1.0      1.0             Rolled back to 2
  6. 4           Mon Oct 3 10:15:13 2016     deployed        alpine-0.1.0      1.0             Upgraded successfully
  1. helm history RELEASE_NAME [flags]

Options

  1.   -h, --help            help for history
  2.       --max int         maximum number of revision to include in history (default 256)
  3.   -o, --output format   prints the output in the specified format. Allowed values: table, json, yaml (default table)

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 10-May-2023