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 --max=4
  2. REVISION   UPDATED                      STATUS           CHART        DESCRIPTION
  3. 1           Mon Oct 3 10:15:13 2016     SUPERSEDED      alpine-0.1.0  Initial install
  4. 2           Mon Oct 3 10:15:13 2016     SUPERSEDED      alpine-0.1.0  Upgraded successfully
  5. 3           Mon Oct 3 10:15:13 2016     SUPERSEDED      alpine-0.1.0  Rolled back to 2
  6. 4           Mon Oct 3 10:15:13 2016     DEPLOYED        alpine-0.1.0  Upgraded successfully
  1. helm history [flags] RELEASE-NAME

Options

  1.       --col-width uint        specifies the max column width of output (default 60)
  2.   -h, --help                  help for history
  3.       --max int32             maximum number of revision to include in history (default 256)
  4.   -o, --output string         prints the output in the specified format (json|table|yaml) (default "table")
  5.       --tls                   enable TLS for request
  6.       --tls-ca-cert string    path to TLS CA certificate file (default "$HELM-HOME/ca.pem")
  7.       --tls-cert string       path to TLS certificate file (default "$HELM-HOME/cert.pem")
  8.       --tls-hostname string   the server name used to verify the hostname on the returned certificates from the server
  9.       --tls-key string        path to TLS key file (default "$HELM-HOME/key.pem")
  10.       --tls-verify            enable TLS for request and verify remote

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 to the kubeconfig file to use
  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 10-Aug-2018